Create a new Monitor
Path parameters
Request body
Aggregate function to apply to the selected values before applying the condition. [none, sum, average, max, min]
The time window to aggregate the selected values. It follows the format of a number followed by a time unit
If true, the monitor is in alert state.
A comparison operation to apply to the value selected by the source_selector [greater_than, greater_than_or_equal_to, less_than, less_than_or_equal_to, equal_to, not_equal_to]
If true, the monitor will not be evaluated.
The last time the monitor was evaluated and routed.
Only relevant when using an aggregate_function. If true, the monitor will be evaluated per device, | rather than across the set of selected devices. If true then if a single device matches the specified criteria, | and alert will be created, otherwise the aggregate function will be applied across all devices.
The time period to wait before routing another event after the monitor | has been triggered. It follows the format of a number followed by a time unit.
If true, alerts will be created, but no notifications will be sent.
A valid JSONata expression that selects the value to monitor from the source. | It should return a single, numeric value.
The type of source to monitor. Supported values are "event" and "heartbeat".
The type of condition to apply to the value selected by the source_selector
For usage monitors: the scope of aggregation. Supported values are "device" and "fleet".
For usage monitors: the type of data usage to monitor. Supported values are "cellular" and "satellite".
For usage monitors: the rolling time window in days to sum usage over (e.g. 30 for 30 days).
Example request
{
"aggregate_window": "10m or 5h30m40s",
"alert_routes": [
{
"email": "example@blues.com"
}
],
"routing_cooldown_period": "10m or 5h30m40s",
"source_selector": "body.temperature"
}Response
Successful operation
Aggregate function to apply to the selected values before applying the condition. [none, sum, average, max, min]
The time window to aggregate the selected values. It follows the format of a number followed by a time unit
If true, the monitor is in alert state.
A comparison operation to apply to the value selected by the source_selector [greater_than, greater_than_or_equal_to, less_than, less_than_or_equal_to, equal_to, not_equal_to]
If true, the monitor will not be evaluated.
The last time the monitor was evaluated and routed.
Only relevant when using an aggregate_function. If true, the monitor will be evaluated per device, | rather than across the set of selected devices. If true then if a single device matches the specified criteria, | and alert will be created, otherwise the aggregate function will be applied across all devices.
The time period to wait before routing another event after the monitor | has been triggered. It follows the format of a number followed by a time unit.
If true, alerts will be created, but no notifications will be sent.
A valid JSONata expression that selects the value to monitor from the source. | It should return a single, numeric value.
The type of source to monitor. Supported values are "event" and "heartbeat".
The type of condition to apply to the value selected by the source_selector
For usage monitors: the scope of aggregation. Supported values are "device" and "fleet".
For usage monitors: the type of data usage to monitor. Supported values are "cellular" and "satellite".
For usage monitors: the rolling time window in days to sum usage over (e.g. 30 for 30 days).
Example response
{
"aggregate_window": "10m or 5h30m40s",
"alert_routes": [
{
"email": "example@blues.com"
}
],
"routing_cooldown_period": "10m or 5h30m40s",
"source_selector": "body.temperature"
}