In Flashduty On-call
Get the integration email address in either of the two ways below. In both cases choose the Email integration type, not Veeam ONE.Use a dedicated integration
- In the Flashduty console, select Channels and open a channel
- Select Settings → Integrations → Dedicated integrations and click Add integration
- Select Email and click Save
- Open the new integration card, copy the email address, then configure the push rules below
Use a shared integration
- In the Flashduty console, go to Integration Center → Alert Events
- Select Email, enter an integration name and copy the email address
- Configure the push rules below
- Set a default route, select a channel and click Save
Configure push rules in Flashduty
Veeam ONE emails carry no alarm ID. An alarm is identified by its alarm name plus the object, and the rules extract these two parts from the email title as the Alert Key. Trigger and resolve emails yield the same key, so a resolve email closes the matching alert.- Set Push mode to Trigger or close alert based on rules
- Add the four rules below in this order. Each rule’s condition is Email title Match the given regex, and the Alert Key is extracted from the Email title
- Under Default rules, choose: if none of the above rules match, discard email
Configure Veeam ONE
The paths below are for Veeam ONE v13, all in the Veeam ONE Client.1
Configure the SMTP server in Veeam ONE
Where: Veeam ONE Client › Settings › Server Settings › Mail Server SettingsEnter your mail server and send a test email to confirm SMTP works.
2
Add the Flashduty email address as an alarm recipient
Add the Flashduty email integration address to the Default email notification group, or to the recipients of the Send email notification alarm action. Set the notification level to Any state, otherwise resolve emails are not sent.HTML or Plain Text both work; the rules read only the email title.
3
Check the notification policy and resolve notifications
Where: Veeam ONE Client › Settings › Server Settings › Notification Policy
4
Trigger an alarm and confirm
First configure the Flashduty push rules above. The test email from step 1 is not an alarm email: sent to the Flashduty address its title matches no rule and the default rule discards it, so it only proves SMTP works. Wait for a real alarm, or raise an Error or Warning alarm on a test object and then let it resolve.Go back to Flashduty. If the integration shows a Latest event time, the Error or Warning email creates an alert and the
Reset/resolved email closes it, the setup works.Email title format
The title of a Mission Critical email comes from Email subject template under Notification Policy → Mission Critical → Edit template. Two common subject formats are shown below. The Veeam ONE documentation does not publish a default, so compare them with the actual content of your own template:
Common values of
%STATUS% (check against the emails you actually receive):
If you change the subject template, update the regexes in the rules to match. You can also set the subject explicitly to template A in Edit template; then only rules 1 and 3 are needed.
Limitations
- Manual resolve: resolving an alarm manually in Veeam ONE sends a summary email (title
Alarm resolve notification) that can list several alarms. The rules cannot close them one by one, so the email is discarded by the default rule. Close these alerts manually in Flashduty, or turn on the auto-resolve timeout in the channel that receives this integration; 24 hours is a reasonable start. - Acknowledge and summary emails: acknowledgements (
Alarm acknowledgement notification) and the Other policy’s summaries (Alarm summary notification) are also summary emails and are discarded by the default rule. - Type and severity: in Flashduty these alerts show the Email integration type, and their severity is always Warning. You can adjust it with alert pipelines based on
Errorin the title. - Merging: alarms with the same alarm name and object merge into one Flashduty alert.