List monitors associated with a log
Authorizations
Path Parameters
The unique identifier of the log
Response
List of monitors for the given log
The unique identifier for the monitor
The name of the monitor
1 - 255"High Error Rate"
the comparison operator of the monitor (ABOVE, ABOVE_OR_EQUAL, BELOW, BELOW_OR_EQUAL, EQUAL, NOT_EQUAL, OUTSIDE). OUTSIDE is two-sided and is only allowed for ANOMALY_DETECTION monitors, which are the only type whose compared value is a signed deviation from a baseline.
BELOW, BELOW_OR_EQUAL, ABOVE, ABOVE_OR_EQUAL, EQUAL, NOT_EQUAL, OUTSIDE "ABOVE"
the threshold the monitor compares against. For PATTERN, USAGE and CHANGE_DETECTION monitors this is a metric value. For ANOMALY_DETECTION monitors it is instead a count of baseline spread units (scaled median absolute deviations, comparable to standard deviations), so it must be greater than 0; a threshold of 3 means "more than 3 spread units away from the baseline centre".
1000
The time window to evaluate the monitor; minimum five minutes, maximum one day
"'Last 20 minutes', 'Last 2 hours', 'Last 1 days'"
The list of actions (notifications) to take when the monitor fires or resolves
1 - 10 elementsThe status of the monitor
OK, NO_DATA, ALERT, WARN "OK"
What the monitor compares its metric against. PATTERN and USAGE compare it to a fixed threshold, CHANGE_DETECTION to the same metric at an earlier time (see compare_to and change_type), and ANOMALY_DETECTION to a trailing baseline of the same series (see evaluation_window and anomaly_algorithm).
PATTERN, USAGE, CHANGE_DETECTION, ANOMALY_DETECTION "PATTERN"
True if an automatic report should be generated when the monitor triggers
Common metadata attached to all persisted resources.
Extra contextual information to add to the monitor
4000"Average response time is over 1 seconds in the last 20 minutes"
the warning threshold value, in the same units as threshold. For ANOMALY_DETECTION monitors it must be greater than 0 and less than threshold whatever the comparison operator, because the comparison is on the magnitude of the deviation.
900
Representation of all the monitored groups and their status
Specify the status to use if a group has no data (no events matched in a time window)
OK, NO_DATA, ALERT, WARN "OK"
The timestamp indicating the ending of the muting. -1 indicates muted forever
1710958395538
Notify only the groups changing the global monitor status, i.e. notifications are sent only for the first group entering ALERT status or for the last group resolving
false
Remove groups with no data after the provided time in milliseconds
0 <= x <= 604800000600000
The timestamp of the last time the monitor fired
1710948395538
Additional monitor configuration
For change detection monitors only. How far back in time the comparison query should be run. Minimum "5 mins ago", maximum "1 month".
"2 hours ago"
For change detection monitors only. Specifies how the change values are calculated, as described in the Bronto documentation.
DIFFERENCE, PERCENTAGE For anomaly detection monitors only, where it is required. The trailing period used to build the baseline the candidate window is compared against, expressed as " ". It must cover at least 10 and at most 1000 monitor windows and be at most 30 days: fewer than 10 windows leaves the baseline permanently degenerate, so the monitor reports healthy and never fires.
"'24 hours', '7 days'"
For anomaly detection monitors only. How the baseline centre and spread are estimated. MEDIAN_MAD uses the median as the centre and the median absolute deviation, scaled by 1.4826 so it reads like a standard deviation, as the spread.
MEDIAN_MAD "MEDIAN_MAD"
Instructions for the AI on what to include in the report, e.g. check for recent deployments, verify the health of the following dependencies: ... etc
The unique identifier for the metric definition that backs this monitor

