The unique identifier of the log
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)
BELOW, BELOW_OR_EQUAL, ABOVE, ABOVE_OR_EQUAL, EQUAL, NOT_EQUAL "ABOVE"
the threshold value of the monitor
1000
The time window to evaluate the monitor. Minimum 5 mins, maximum 1 day.
"'Last 20 minutes', 'Last 2 hours', 'Last 1 days'"
The list on actions (notifications) to take when the monitor fires or resolves
1 - 10 elementsThe timestamp when the monitor was created
1710948395538
The status of the monitor
OK, NO_DATA, ALERT, WARN "OK"
PATTERN, USAGE, CHANGE_DETECTION True if an automatic report should be generated when the monitor triggers
Extra contextual information to add to the monitor.
4000"Average response time is over 1 seconds in the last 20 minutes"
The filter used to identify events to monitor on.
2000"response_time and response_status=200"
The key that identifies the numeric value to monitor
50"response_time"
The list of keys to group by
["region", "host"]The function to compute (MIN, MAX, COUNT, SUM, AVG)
MIN, MAX, COUNT, SUM, AVG, AVERAGE "AVG"
the warning threshold value
900
The list of log identifiers to filter for matching events
1 - 50 elementsThe tags filters for selecting the datasets. Each from_tags should be in the form <key>:<value>, e.g. environment:production.
When multiple from_tags are provided, filters on the same tag key are evaluated with OR logic, while filters on tags with different keys
are evaluated with AND logic (facet style search). e.g. [environment:production, team:A, team:B] will include all production datasets where
the team tag is either B or A.
One of either the logs or the from_tags parameters must be specified.
If both are specified then from_tags takes precedence, and the logs value is ignored.
1 - 50 elements1 - 250["environment:production"]Representation of all the monitored groups and their status
[
{
"group_id": "region:EU,host:100",
"status": "OK",
"groups": { "region": "EU", "host": 100 }
},
{
"group_id": "region:EU,host:101",
"status": "ALERT",
"groups": { "region": "EU", "host": 100 }
}
]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. e.g. notifications are sent only for the first group going in ALERT status or for last group resolving)
false
Remove groups with no data after the provided time in milliseconds
600000
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', '1 days ago'"
For change detection monitors only. Specifies how the change values are calculated, as described in the Bronto documentation.
DIFFERENCE, PERCENTAGE Instruction 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 that backs this monitor