Workflow | Alert setup

Setting up an alert in Digi Remote Manager can be thought of as a three-part process: review what exists, create the rule and define when it triggers, and then choose who is notified.

Step

Considerations

Look at existing alerts and activity on the Lists tab.

  • Look at existing system and configured alert details and history to avoid duplicating a rule you may already have.

  • Identify whether the issue you care about is recurring or a one-off (which affects how sensitive the trigger should be).

  • Confirm the target is clear:

    • Which device(s) or group(s) should be covered?

    • Is the device/group naming consistent enough that others will recognize it?

  • Check for “alert noise” signals:

    • Are there alerts that fire too often?

    • Are there alerts that never fire (possibly too strict or disabled)?

Step

Considerations

Create a configured alert and define when it should trigger.

  • Choose the general alert category/type that matches what you’re trying to detect (e.g., offline condition vs. data threshold).

  • Name it so it’s actionable: include the scope (site/group/device family) and the condition (what’s wrong).

  • Decide whether this alert is meant for:

    • Immediate operational response (on-call), or

    • Reporting/compliance/trending (less urgent delivery).

  • Specify the trigger threshold clearly (what value/state causes the alert to fire).

  • Add “stability” so it doesn’t flap:

    • Consider a time window (e.g., “for 5 minutes”) or persistence requirement if available.

  • Define how it should reset/clear:

    • Should it clear automatically when the condition returns to normal?

    • Should it require manual reset as part of your process?

  • Set the scope intentionally:

    • Single device vs. group-wide

    • If group-scoped, confirm the group membership is maintained (new devices added later may inherit the alert).

  • Choose severity/priority (if available) based on impact:

    • Safety/production outage vs. minor degradation vs. informational.

Create a notification list for the new alert.

  • Decide who gets notified.

  • Choose notification style based on urgency:

    • Immediate email for operational issues

    • Summary/digest for lower-priority or high-volume alerts

  • Decide ownership and escalation:

    • Who is responsible first (primary) and who is backup (secondary)?

    • Should distribution lists be used instead of individuals to avoid gaps?

  • Prevent notification overload:

    • If it’s likely to fire frequently, prefer summaries or narrow the recipient list.

  • Make sure messages will be meaningful:

    • Ensure the alert name and context (device/group) are enough for the recipient to take action without hunting.

Once the alert is configured and enabled, Digi Remote Manager will monitor the scoped devices automatically and deliver notifications according to the notification list you configured.