From 05ed7cb24df03f6999526dfcff3d4995e22d1062 Mon Sep 17 00:00:00 2001 From: pvallone Date: Thu, 29 Aug 2024 13:02:46 -0500 Subject: [PATCH] Expose active alarm cleanup and alarm limit config in the user-facing values file (#213) --- .../templates/systemlink-values.yaml | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/getting-started/templates/systemlink-values.yaml b/getting-started/templates/systemlink-values.yaml index 574a8160..83c81959 100644 --- a/getting-started/templates/systemlink-values.yaml +++ b/getting-started/templates/systemlink-values.yaml @@ -465,6 +465,29 @@ alarmservice: ## The amount of time inactive alarms will be retained in the database ([d.]hh:mm[:ss] format). ## inactiveAlarmCleanupInterval: 30.00:00 + + activeAlarmCleanup: + ## The amount of time active alarms will be retained in the database since they were + ## last updated ([d.]hh:mm[:ss] format). + ## + interval: 90.00:00 + ## Whether to limit active alarm cleanup to only affect active alarms whose most recent + ## transition has a CLEAR transition type. + ## + onlyCleanUpClearAlarms: false + + ## The total number of alarms the service supports creating, including + ## both active and inactive alarms. Must be greater than activeAlarmLimit. + ## The service will return an error if this limit is exceeded. Increasing + ## this limit requires tuning of database resources. + ## + alarmLimit: 100000 + + ## The total number of active alarms the service supports creating. Must be less + ## than alarmLimit. The service will return an error if this limit is exceeded. + ## Increasing this limit requires tuning of database resources. + ## + activeAlarmLimit: 10000 ## Configuration for the Grafana dashboard provider. ##