Skip to main content
Raritan PX-Series PDUs send email through the Send email action of an event rule, and the email subject and message can be customized. The Flashduty email integration receives these emails and uses rules on the email title to decide whether each one triggers or resolves an alert, so no separate Raritan integration is needed: create an email integration in Flashduty, add its email address to the PDU’s Send email action, set the email subject to the fixed format below, and configure the push rules.

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 Raritan.

Use a dedicated integration

  1. In the Flashduty console, select Channels and open a channel
  2. Select Settings → Integrations → Dedicated integrations and click Add 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, go to 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

Configure push rules in Flashduty

The subject format below puts the device name, the event rule name and an assertion flag in the title. The flag 1 means the event condition became true and 0 means it cleared. The rules extract the device name and event rule name as the Alert Key. Trigger and resolve emails yield the same key, so a resolve email closes the matching alert.
  1. Set Push mode to Trigger or close alert based on rules
  2. Add the two 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
  3. Under Default rules, choose: if none of the above rules match, discard email
Rule 1: close the alert
Rule 2: trigger an alert
The close rule comes before the trigger rule. The default rule discards emails that do not follow the subject format, such as default emails sent by other event rules, so they don’t create alerts that can never close on their own.

Configure Raritan PX

The paths below come from the Raritan PX-Series PDU user guide (firmware 4.3.11) and are used in the PDU web interface.
1

Configure the SMTP server in Raritan PX

Where: PDU web interface › Device Settings › Network Services › SMTP ServerConfigure the mail server; the Send email action uses it by default.
2

Create a Send email action

Where: PDU web interface › Device Settings › Event RulesCreate an action and fill in:
[DEVICENAME] (the device the event occurred on), [EVENTRULENAME] (the name of the matching event rule) and [ISASSERTED] (1 when the event condition became true, 0 when it became false) are placeholders listed in the user guide; they are replaced with actual values when the email is sent. A rendered subject looks like:
The rules read only the email title; the default or a custom message body both work.
3

Create an event rule that uses the action

Where: PDU web interface › Device Settings › Event RulesCreate a rule and fill in:
4

Trigger the event and confirm

First configure the Flashduty push rules above. Make the monitored condition true once (for example by temporarily lowering the sensor threshold), then restore it. A test-email button in the PDU interface only proves that SMTP works; the subject placeholders may not be substituted, so it does not prove the rules match.Go back to Flashduty. If the integration shows a Latest event time, the email with flag 1 creates an alert and the email with flag 0 closes it, the setup works.

Limitations

  • Unique event rule names: the Alert Key is built from the device name and the event rule name, so events that share one rule name merge into one alert. Create a separate event rule with its own name for each event you want to monitor.
  • Trigger condition: with Asserted only, the PDU sends trigger emails but no resolve emails, and alerts do not close automatically.
  • 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 the title.