...
| Info |
|---|
Authentication: use “Authorization” in your HTTP header with your query key. |
For every query, the time pointer will be moved to the time of the query. Next query will then get all anomaly alerts since last query.Authentication: use “Authorization” in your HTTP header with your query key.
This means that every time you read an unread alert, it will no longer be “visible” through this API.
However, since the alert is now in “ongoing” status, you can query it through the “current” API.
Example response
| Code Block |
|---|
[
{
"severity": "medium",
"event_type": "updated",
"event_occured": "2024-07-11T07:28:00Z",
"id": "668f1d1a6ea102403a5298b5",
"items": [
{
"node": {
"id": 144,
"name": "Execution Manager. http://10.0.1.10:8778/jolokia",
"system": {
"id": 4,
"name": "http://10.0.1.10:8778/jolokia"
}
},
"metrics": [
{
"id": "50060171-414b-4cbd-8534-5b0d9338c86b",
"name": "Average Execution Time",
"metric_type": "int",
"aggregation": "avg",
"severity": "severe",
"started": "2024-07-10T23:42:00Z",
"updated": "2024-07-11T00:12:00Z"
},
{
"id": "0dee40ce-19bf-4717-ac9e-1465f8c62cf3",
"name": "Running Execution Estimated Count",
"metric_type": "int",
"aggregation": "avg",
"severity": "severe",
"started": "2024-07-11T07:23:00Z",
"updated": "2024-07-11T07:28:00Z"
}
]
}
]
} |