Alarms with the same unique ID not updating existing open alarms.

Products

• DX SaaS

Issue/Introduction

Incoming alerts sharing an identical alarm_unique_id definition (e.g., $['host']%//%:%//%$['application']%//%-%//%$['alertid']) continuously create duplicate open alarms instead of updating the existing active alarm.

The issue recurs at regular intervals matching the configured alarm Time-To-Live (TTL).

Cause

DE678306: Setting alarm_ttl_mins to a short window (e.g., 30 minutes) causes the internal TTL tracking in RESTmon to expire after that duration. Once expired, any subsequent payload carrying the same alarm_id is evaluated as a brand-new alarm rather than a status update to the existing entry.

Resolution

Increase the TTL value to 24 hours (1440 minutes) following procedure shown below:

• Navigate to DX-RESTmon-xxx\config\restmon.json.
• Locate alarm_ttl_mins in the profile section.
• Change the value from 30 to 1440 (or delete the alarm_ttl_mins line entirely).
• Save the file and restart the dx-restmon service to apply changes.