Create monitor
Create monitor
Body
Configuration for a monitoring rule. Monitors can be configured to: - Check threshold values (e.g., CPU usage > 90%) - Match specific events in logs - Detect anomalies based on historical patterns Each monitor runs on a specified interval and can trigger notifications through configured notifiers.
application/json| Property | Type | Description |
|---|---|---|
alertOnNoData | boolean | Whether to alert when no data is received |
aplQuery | string | APL (Axiom Processing Language) query string used for monitoring. This query defines what data to analyze and how to process it. At least one of aplQuery or mplQuery must be provided. |
columnName | string | Name of the column to monitor |
compareDays | number<int64> | Number of days to compare for anomaly detection |
createdAt | string<date-time> | Timestamp when the monitor was created |
createdBy | string | ID of the user who created the monitor |
description | string | Detailed description of the monitor's purpose |
disabled | boolean | Whether the monitor is currently disabled |
disabledUntil | string<date-time> | Timestamp until when the monitor should remain disabled |
intervalMinutes | integer<int64> | How frequently the monitor should run, in minutes. Minimum value is 1 minute. |
mplQuery | string | MPL (Metrics Processing Language) query string for metrics-based monitoring. Use this as an alternative to aplQuery for metrics datasets. At least one of aplQuery or mplQuery must be provided. |
name | stringRequired | Name of the monitor |
notifierIds | string[] | List of notifier IDs that will receive alerts. Notifiers can be email, Slack, webhook endpoints, etc. |
notifyByGroup | boolean | Whether to group notifications |
notifyEveryRun | boolean | Whether to send notifications on every check |
operator | string | Comparison operator for threshold checks: - Below: Trigger when value < threshold - BelowOrEqual: Trigger when value <= threshold - Above: Trigger when value > threshold - AboveOrEqual: Trigger when value >= threshold - AboveOrBelow: Trigger when value is outside a range |
rangeMinutes | integer<int64> | Time window to evaluate in each check, in minutes. For example, "last 5 minutes of data" |
resolvable | boolean | Whether the alert can be manually resolved |
secondDelay | number<int64> | Delay in seconds before triggering the alert |
skipResolved | boolean | Whether to skip resolved alerts |
threshold | number<double> | Threshold value for triggering the alert |
tolerance | number | Tolerance percentage for anomaly detection |
triggerAfterNPositiveResults | number<int64> | Number of positive results needed before triggering |
triggerFromNRuns | number<int64> | Number of consecutive check runs that must fail before triggering an alert. Use this to avoid alerting on temporary spikes. |
type | stringRequired | Type of monitoring check to perform: - Threshold: Compares a numeric value against a threshold - MatchEvent: Looks for specific events or patterns - AnomalyDetection: Identifies unusual patterns based on historical data |
updatedAt | string<date-time> | Timestamp when the monitor was last updated |
Request
Try itRun this request against your Axiom organization
Credentials stay in this browser tab and are only sent to Axiom when you run the request.
Response
200Monitor