Static thresholds for custom metric events

A static threshold represents a hard limit a metric should not violate. The limit can be a single value or a range. As static thresholds don't change over time, they are an important monitoring tool, helping you to define critical boundaries of normal operation.

It's important to chose between a static threshold and an adaptive baseline, depending on your use case.

For example, you can use a static threshold to set a limit for total memory usage by a well-known process. In this case, a static threshold is superior to an adaptive threshold, because if memory consumption slowly grows over time, the adaptive threshold simply changes with it, raising no problems and leading, eventually, to a hidden memory leak.

In the illustrations below, memory consumption steadily increases over 30 days. A statically defined threshold of 40 MB will catch the process's abnormal behavior, while an adaptive baseline will increase along with the metric value.

static threshold

adaptive baseline

Apart from the threshold value, you can also specify how often the threshold must be violated within a sliding window of time to raise an event (violations don't have to be successive). It helps you to avoid alerting too aggressively on single threshold violations. You can set a sliding window of up to 60 minutes.

Static threshold parameters

By default, any 3 minutes out of a sliding window of 5 minutes must violate your threshold to raise an event. That is, an event would require 3 violating minutes within any 5-minute sliding window.