Metric policies overview
Metric policies allow you to define how your metric data is handled (dropped, stored, or used for anomaly detection), and to control the information and values that determine when an anomaly is detected for ingested time series data. The anomalies may, depending on policy settings, become alerts, and then get correlated into incidents. For more information on alerts and incidents, see Events, alerts, and incidents.
Access the Metric Policies interface by navigating to Correlate & Automate > Metric Policies.
This feature area lets you control the way that metric data and anomalies are handled.
The Default Metric Policy ensures that Moogsoft Cloud stores all ingested metrics (it can be modified to drop instead). It also detects anomalies using adaptive anomaly detection with some suggested initial settings. You can modify the Default Metric Policy to customize anomaly detection, or create your own policies. All custom metric policies are evaluated first, with the Default Metric Policy applying only to metric data that did not match any other policies.
Important
Anomalies are detected using the default configuration in the Default Metric Policy until you modify it or create additional policies.
On the Metric Policies page, you can perform the following actions:
Create a policy
Use this section to create a new metric policy. It is a good idea to use a descriptive name for each policy because the Alerts and Incidents pages display the names of the policies responsible for the anomalies behind the displayed alerts and incidents.
Allow at least five minutes for a new policy to take effect to allow for data caching and processing.
For information on metric policy settings and instructions for creating a new policy, see Configure metric policies.
Search for a policy
You can search for a policy by:
Policy name
Any keyword in the policy scope
The name of the user who created it
Begin typing in the Search box and a matching list of policies displays below it.
Reorder policies
Every metric ingested in Moogsoft is checked against the list of metric policies in order, from top to bottom, until the metric matches the scope of a policy. The first policy in the list with a matching scope is applied to the metric. All other policies are skipped for that metric. For this reason, you may decide to reorder your list of metric policies. It is usually preferable to list the more specific policies at the top of the list and the more general policies toward the bottom.
Note that if a metric does not match any user-defined metric policy, then the default policy is applied to it.
Click the vertical three dot menu at the right of the Create New Policy button.
Click Edit Policies Order.
Click and drag a policy to a new location to change the order.
When your policies are in the preferred order, click Save.
Limitations
You can create a maximum of 100 policies. Visit the Moogsoft support site and open a request if you need to exceed this limit.