Configure monitors

This page explains how to configure monitors.

Edit monitors

To edit an existing monitor:

1. Click the Monitors tab.
2. Click the monitor in the list that you want to edit.
3. In the top right, click Edit monitor.
4. Make changes to the monitor.
5. Click Save.

Disable monitors

Disable a monitor to prevent it from running for a specific amount of time.

To disable a monitor:

1. Click the Monitors tab.
2. Click the monitor in the list that you want to disable.
3. In the top right, click Disable monitor.
4. Select the time period for which you want to disable the monitor.
5. Click Disable monitor.

Axiom automatically enables the monitor after the time period you specified.

Enable monitors

To enable a monitor:

1. Click the Monitors tab.
2. Click the monitor in the list that you want to enable.
3. In the top right, click Enable monitor.
4. Click Enable monitor.

Clone monitors

To clone a monitor:

1. Click the Monitors tab.
2. Click the monitor in the list that you want to delete.
3. In the top right, click More.
4. Click Clone monitor.

Delete monitors

To delete a monitor:

1. Click the Monitors tab.
2. Click the monitor in the list that you want to delete.
3. In the top right, click More.
4. Click Delete monitor.

Trigger after N consecutive failures

By default, a monitor triggers on the first check run that crosses the threshold or matches the condition. To reduce noise from transient spikes, you can require the condition to hold across multiple consecutive check runs before the monitor triggers.

This setting is not available in the Axiom UI. Configure it using the REST API.

Set triggerFromNRuns in the request body when creating or updating a monitor:

{
  "triggerFromNRuns": 3
}

With triggerFromNRuns set to 3, the monitor only triggers after three consecutive check runs where the condition is met. If any run does not meet the condition, the count resets. This is useful when you want to avoid alerting on brief, temporary anomalies.

triggerFromNRuns applies to threshold monitors and anomaly monitors. The minimum value is 1, which is the default behavior (trigger immediately).

To verify the current value, use the Get monitor endpoint and check the triggerFromNRuns field in the response.