System Administration > Monitoring > Alarms And Events

Get Alarm identified by alarm-id.

Returns alarm associated with alarm-id. If HTTP status 404 is returned,
this means the specified alarm-id is invalid or the alarm with alarm-id
has been deleted. An alarm is deleted by the system if it is RESOLVED
and older than eight days. The system can also delete the remaining
RESOLVED alarms sooner to free system resources when too many alarms
are being generated. When this happens the oldest day's RESOLVED alarms
are deleted first.

Request:

Method:
GET
URI Path(s):
/api/v1/alarms/<alarm-id>
Request Headers:
n/a
Query Parameters:
n/a
Request Body:
n/a

Example Request:

GET /api/v1/alarms/daabc688-3a90-4545-9af8-23e1b045e6f3

Successful Response:

Response Code:
200 OK
Response Headers:
Content-type: application/json
Response Body:
Alarm+

Example Response:

{ "id": "daabc688-3a90-4545-9af8-23e1b045e6f3", "status": "OPEN", "feature_name": "manager_health", "event_type": "manager_cpu_usage_high", "feature_display_name": "Manager Health", "event_type_display_name": "CPU Usage High", "node_id": "8af5d6d7-e8bc-454d-90bd-4824782216ea", "last_reported_time": 1551994806, "description": | "The CPU usage for the manager node identified by appears to be\nrising.", "recommended_action": | "Use the top command to check which processes have the most CPU usages, and\nthen check \/var\/log\/syslog and these processes' local logs to see if there\nare any outstanding errors to be resolved.", "node_resource_type": "ClusterNodeConfig", "severity": "WARNING", "entity_resource_type": "ClusterNodeConfig", }

Required Permissions:

read

Feature:

system_alarms_events

Additional Errors: