Pro Server can send Email Notifications when any connected DriveWorks Autopilot agent disconnects unexpectedly (for example when the machine hosting the Autopilot agent powers off).
Please Note
Any changes to the settings require saving and the Pro Server Service stopped (if running) and restarted.
Check this setting to enable Pro Server to send email notifications.
These settings control how often agents are monitored, when to resume monitoring and how many emails are sent.
This CRON expression defines when Pro Server should check for an Autopilot heartbeat.
CRON expressions are used to describe the timing of an event (checking for an Autopilot heartbeat).
The default value:
* * * * *
Will check for a heartbeat every minute.
For help setting up more complex schedules please see crontab guru.
DriveWorks Pro Server will classify a connection as failed after 2 minutes without a response.
The check heartbeat CRON expression result will begin after this time.
For example when the CRON expression is set to check every minute (the default), the failure notification will be sent between 2 and 3 minutes after.
The number of failed connection attempts before Pro Server sends a notification email.
The default value of 1 will send a notification immediately a failed connection occurs.
This setting is intended to prevent notifications being sent for events other than a computer crash, for instance a network drop that could correct itself.
If you experience frequent network drops consider increasing this value.
A CRON expression representing when to resume heartbeat monitoring after an email has been sent.
The default value:
* * * * *
Will resume monitoring one minute after the previous email has been sent.
The maximum number of emails to send out per agent before stopping the monitoring process.
The default value of 1 will send one notification only.
To resume monitoring an agent that has stopped, launch the failed DriveWorks Autopilot, log in to the required Group, and click Start.
Pro Server uses a more modern SMTP Client than Email Settings (for Autopilot) to send emails.
Settings applied to allow DriveWorks Autopilot to send emails will be different to Pro Server Email Server Settings.
Please check with your mail provider for recommended SMTP settings.
This is the name of the SMTP server which will be used to send the email.
For example:
Please check with your mail provider for SMTP settings.
Select from:
Please check with your mail provider for SMTP settings.
This is usually:
Please check with your mail provider for SMTP settings.
The username used to log in to the mail server.
The password used to log in to the mail server.
When using a mail provider that requires 2FA see Two-factor authentication below.
The email address for the account the notification will be sent from.
The email address to send the notification to.
Multiple addresses can be applied by separating each address with a semi-colon (;).
For example:
me@myemail.com ; you@youremail.com
The text to include in the subject line of the email.
The text to iclude in the body of the email.
The following special variables are available for use in the email body:
References the agents name that cannot be contacted.
This will comprise of the following:
<domain>\<user>@<machine name>
References the machine running the agent that cannot be contacted.
References the user running the agent that cannot be contacted.
References the time the heartbeat that failed was requested.
This is given as the date followed by the exact time.
If the account has Two-factor authentication (also known as 2-Step Verification) an App Password will need to be generated in the mail account.
For Gmail:
Port
The Port number, when using 2FA for Gmail is 587.
Pro Server email notifications are logged in the Windows Event Viewer.
From the Windows search bar type Event Viewer and click the Event Viewer app.
Pro Server will create an Information log for each Autopilot agent being monitored.
An Information log will be created for any Autopilot agent where monitoring has stopped.
Monitoring will stop when the Emails Per Agent setting has been reached.
To resume monitoring an agent that has stopped, launch the failed DriveWorks Autopilot, log in to the required Group, and click Start.
An Error log will be created if there was a problem sending an email notification.
The log will contain information for the error encountered, to view the information:
To trigger an email notification a DriveWorks Autopilot Agent needs to unexpectedly fail.
To replicate a sudden crash, please follow the steps below:
This will allow the messages that DriveWorks Pro Server posts to be viewed.
DriveWorks Autopilot must be started for monitoring to commence.
The Windows Event Viewer, on the Pro Server machine, will update with an entry that displays the message "Starting to monitor Autopilot Agent...".