> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flashduty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Veeam Service Provider Console alert integration

> Veeam Service Provider Console sends alarm notifications by email; use a Flashduty email integration with rules to trigger VSPC alerts.

Veeam Service Provider Console (VSPC) sends alarm notifications by email. The Flashduty [email integration](/en/on-call/integration/alert-integration/alert-sources/email) receives these emails and creates alerts from the email title with rules, so no separate VSPC integration is needed: create an email integration in Flashduty, add its email address as an alarm recipient in VSPC, set the VSPC alarm email subject to the fixed format below, and configure the push rules.

<div className="hide">
  ## 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 Service Provider Console.

  ### Use a dedicated integration

  1. In the Flashduty console, select **Channels** and open a channel
  2. Select **Settings** → **Integrations** → **Dedicated integrations** and click **Add an integration**
  3. Select **Email** and click **Save**
  4. Open the new integration card, copy the **email address**, then configure the push rules below

  ### Use a shared integration

  1. In the Flashduty console, select **Integration Center → Alert events**
  2. Select **Email**, enter an integration name and copy the **email address**
  3. Configure the push rules below
  4. Set a default route, select a channel and click **Save**
</div>

## Configure push rules in Flashduty

***

VSPC emails carry no alarm ID. The subject format below puts the company, location and alarm name in the title, and the rule extracts these three parts as the Alert Key. Emails with the same company, location and alarm name merge into one alert. The alarm status is not part of the Alert Key, so when an alarm changes from Warning to Error the existing alert is updated instead of a new one being created.

1. Set **Push mode** to **Trigger or close alert based on rules**
2. Add the one rule below: the condition is **Email title** **Match** the given regex, the type is **Trigger alert**, and the Alert Key is extracted from the **Email title**
3. Under **Default rules**, choose: if none of the above rules match, **discard email**

Rule 1: trigger an alert

```
Condition: Email title  Match  /^VSPC (Error|Warning) \| /
Regex: /^VSPC (?:Error|Warning) \| (.+) \| (.+) \| (.+)$/
```

The default rule discards unmatched mail so that emails with the Information status don't create alerts.

## Configure Veeam Service Provider Console

***

The paths below come from the VSPC documentation and require administrator rights.

1. **Email server**: go to **Configuration** → **Server Settings** → **Email Server** and configure the SMTP server (server address, port, encryption)
2. **Notification frequency**: in the **Alarms** section, set the frequency slider to **Emails on every event**. **Summary emails only** sends a daily digest, which the rules cannot process one alarm at a time
3. **Subject**: in the **Alarms** section, set **Subject** to:

```
VSPC %alarmStatus% | %company% | %location% | %alarmName%
```

`%alarmStatus%`, `%company%`, `%location%` and `%alarmName%` are the variables VSPC supports in alarm notification subjects. A rendered subject looks like:

```
VSPC Error | Contoso | London | Backup job failed
```

4. **Recipients**: by default VSPC sends alarm emails to location administrators and company administrators. To send them to Flashduty, go to **Configuration** → **Templates** → **Predefined Alarms** tab, select an alarm and click **Edit**, click **Add** at the **Actions** step, choose **Send email notification** in **Action**, enter the Flashduty email integration address in **Value**, and set the condition to **Errors and warnings**
5. **Email format**: the rules read only the email title; the body format does not affect matching

## Limitations

***

* **No resolve email**: by default VSPC sends email when a new alarm is raised or when an existing alarm changes to Error or Warning, so the rules cannot close alerts automatically. Turn on the [auto-resolve timeout](/en/on-call/channel/create-edit) in the channel that receives this integration; 24 hours is a reasonable start. You can also close alerts manually in Flashduty.
* **Object merging**: the subject variables do not include an object name, so alarms with the same name on different objects under the same company and location merge into one Flashduty alert.
* **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](/en/on-call/integration/alert-integration/alert-pipelines) based on `Error` in the title.