Understanding KloudMate Alarms

developers create custom kloudmate alarms to monitor events critical to their applications these alarms use a set of evaluation criteria to determine whether the alarm triggers key concepts alarm rule an alarm rule contains evaluation criteria one or more queries, expressions, and conditions it specifies the evaluation frequency and the duration a condition must remain true before the alarm triggers alarm query a query provides configurational instructions to request data from a source kloudmate alarms support aws cloudwatch or kloudmate as data sources alarm expressions expressions manipulate, reduce, or transform data from queries using math operations and reduction functions they set conditions against raw query data or transformed results notification channel notification channels are chatops and communication platforms that receive alarm notifications kloudmate integrates with popular tools like slack, email, and more notification tags tags add name value attributes to alarms, enabling cross referencing and mapping to notification policies notification policies notification policies define when, where, and how to send alarm notifications they route alerts to a specific channel when an alarm’s tags match the policy’s tags alarm labels alarm labels are key value pairs with additional information about the alarm rule kloudmate assigns labels to alarm queries based on query dimensions alarm expressions inherit labels from their source queries labels determine if operations between queries/expressions are allowed operations work if labels match exactly or one is a subset of the other view labels when previewing alarms multi dimensional alarms kloudmate supports multiple alarms per rule, called multi dimensional alarms for example, a rule checking lambda throttling creates one alarm per throttled function workflow of kloudmate alarms an alarm rule retrieves data from the selected source using queries reduces or transforms query results with expressions compares queries, expressions, or thresholds using conditions triggers only if the condition holds for the defined duration once the condition is met and remains true for the defined duration, kloudmate compares the notification tags added to the alarm against the tags specified in notification policies when tags match exactly (all policy tags must exist on the alarm), kloudmate sends the notification to the notification channel configured in that matching policy if no tags are specified in a notification policy, it matches all alarms regardless of their tags the following diagram gives a general outline of the lifecycle of a kloudmate alarm kloudmate alarm states alarm states show current status filter and view alarms by state firing/alerting alarm active longer than configured duration pending alarm active but shorter than threshold duration normal no firing or pending—everything works as expected error error occurred during evaluation no data no data received for the configured time window related resources setting up kloudmate alarms https //docs kloudmate com/setting up kloudmate alarms writing expressions for kloudmate alarms https //docs kloudmate com/writing expressions for kloudmate alarms