Alerts & Notifications

New to Metricly? Use this page as an overview for the features related to Alerts, Events, Policies, and Notifications. For a more technical walkthrough on each, see our related articles. Alerts Alerts are a continuous series of events. They group anomalous behavior and enable you to view open (active) or closed (inactive) incidents. The Open Policies list is the first you see when navigating to the Alerts menu. This list is updated every 30 seconds.

Alerts Page

The Alerts page shows a list of all your configured policies, both enabled and disabled. It includes: Policy name Number of elements in scope Filters on the policy State of the policy (Enabled/Disabled) Current status (OK, Info, Warning, Critical). This page has additional filters to display all Open and Closed policies. Filtering by Open will display only the policies that are currently (Now) violating a set condition(s).

Choose Duration

Duration is the consecutive length of time for which all the conditions in a policy must be met before an event or other optional notification is created. The default setting for metric condition duration is 5 minutes; the default (and only) setting for external event condition duration is real-time. Because Metricly aggregates data on five-minute cycles, the duration for metric conditions must be at least 5 minutes. By setting the duration of ExamplePolicy X to 10 minutes, an event will not be created in Metricly until all the conditions in ExamplePolicy X have been met for the same period of 10 consecutive minutes.

Choose Scope

The scope of a policy defines which element(s) get assigned to that policy. A policy can use a combination of criterion to narrow its selection; for example, all elements tagged with region-east + EC2 as a type. Scope Methods When using multiple fields, an element must meet each criterion to be included in the policy’s scope. Name Contains or Name Excludes Input a string of characters into the Name Contains or Name Excludes field.

CloudWatch Events

Through a combination of SNS Notifications, Metricly’s Webhook integration, and an external event conditions policy filter, you can push event logs from your AWS services to Metricly and act on them in the UI. This works across several AWS services. Once set up, these logs can be divided further on the policy level (through matching value strings in the log message and categorized by severity). Policies for your event logs can also be set up with various notifications through email, slack, and others.

Create Conditions

When you are creating conditions, the Policy Editor counts the number of metrics that apply to the conditions you have set. To view those metrics, click on the link. This link opens the list of matching metrics in a new tab. Create a Metric Condition Navigate to Alerts > New Policy > Conditions > Add Condition > Add Metric Condition. To edit an existing policy, Navigate to Alerts > Show All Policies > Click Policy Name > Edit Policy > Conditions > Add Metric Conditions.

Create External Event Conditions

External Event conditions for policies are typically used in conjunction with Webhook integrations. See the Webhook integration setup or Webhook API documentation for more information. Open Policy Editor. Click Conditions. Click Add Condition, then select Add External Event Condition. Type into the fields to create a proper filter: Message Contains: A regex statement that attempts to match a word or phrase in the event message. Title Contains: A regex statement that attempts to match a word or phrase in the event’s title.

Create or Edit a Policy

Create, edit, delete, enable, and disable policies with the Policy Editor. You can also use Policy Editor to enable and disable notifications. Open the Policy Editor. Navigate to Alerts > + Add New Policy. Begin crafting your policy at Step 1: Scope. You can also open an existing policy and click Edit Policy. Policies that correspond to inactive datasources cannot be edited. The top of your policy has 3 important fields: