Business services and infrastructure are always changing. Now, instead of needing to understand the expected performance of an individual service so you can manually specify a static threshold, you can easily use dynamic thresholds by creating anomaly alert conditions that cover all of your services and infrastructure. These adjust to accommodate the expected fluidity and volatility of your business.
We’ve expanded our existing dynamic anomaly alerting, which previously had to be individually configured for each individual signal, to allow one alert configuration to apply dynamic thresholding across up to five thousand related time series of a particular service or entity. This greatly simplifies the process of adding alert coverage to all of your entities, by all of your teams. No team should be sitting on the sidelines, and missing the benefits of incident response.
Setting static thresholds can be intimidating to many engineers. It is easy to create dynamic anomaly alert conditions that cover all of your services and infrastructure. Simply add the “FACET” clause to the NRQL queries you are using, and specify the metadata attributes that differentiate the signals that you want to monitor. Then, simply drag a slider to set and tune the sensitivity.