Adjust how many alarms you can create in the SystemLink Enterprise Alarm Service.

Introduced in September 2024

If you reach an alarm limit, the Alarm Service returns an error. This error occurs when Alarm Service processes a new alarm creation request. You can monitor the number of active and inactive alarms with the counter metric that the Alarm Service emits. For more information, refer to Performance Metrics for the Alarm Service.
SystemLink Enterprise has the following default limits for active alarms and total alarms.
  • Active alarms: The Alarm Service allows you to create up to 10,000 active alarms. If you reach this limit, you must complete one of the following actions.
    • Delete some active alarms.
    • Deactivate some active alarms. You can force alarms inactive by using the acknowledge API. Set the forceClear flag on the request to true.
  • Total alarms: The Alarm Service allows you to create up to 100,000 alarms total. This limit includes both active alarms and inactive alarms. If you reach this limit, you must delete some alarms before you can create new alarms.
To change the alarm limits, complete the following steps.
Note Creating too many alarms can degrade performance. If you must increase the alarm limits, consider increasing the MongoDB database resources for the Alarm Service.
  1. Open the systemlink-values.yaml file.
  2. Make the changes that align with your goal.
    OptionDescription
    Configure the limit for active alarms. Modify the value of alarmservice.activeAlarmLimit.
    Configure the limit for total alarms. Modify the value of alarmservice.alarmLimit.