List Alarms Status
GET {{baseUrl}}/alarms/status?compartmentId={{compartment_ocid}}&compartmentIdInSubtree=false&page=&limit=576&sortBy=displayName&sortOrder=ASC
List the status of each alarm in the specified compartment. For important limits information, see Limits on Monitoring.
This call is subject to a Monitoring limit that applies to the total number of requests across all alarm operations. Monitoring might throttle this call to reject an otherwise valid request when the total rate of alarm operations exceeds 10 requests, or transactions, per second (TPS) for a given tenancy.
Request Params
| Key | Datatype | Required | Description |
|---|---|---|---|
compartmentId | string | (Required) The OCID of the compartment containing the | |
| resources monitored by the metric that you are searching for. Use tenancyId to search in | |||
| the root compartment. |
Example: ocid1.compartment.oc1..exampleuniqueID
|
| compartmentIdInSubtree | boolean | | When true, returns resources from all compartments and subcompartments. The parameter can
only be set to true when compartmentId is the tenancy OCID (the tenancy is the root compartment).
A true value requires the user to have tenancy-level permissions. If this requirement is not met,
then the call is rejected. When false, returns resources from only the compartment specified in
compartmentId. Default is false.
|
| page | null | | For list pagination. The value of the opc-next-page response header from the previous "List" call.
For important details about how pagination works, see List Pagination.
|
| limit | number | | For list pagination. The maximum number of results per page, or items to return in a paginated "List" call.
For important details about how pagination works, see List Pagination.
Default: 1000
Example: 500
|
| displayName | string | | A filter to return only resources that match the given display name exactly.
Use this filter to list an alarm by name. Alternatively, when you know the alarm OCID, use the GetAlarm operation.
|
| sortBy | string | | The field to use when sorting returned alarm definitions. Only one sorting level is provided.
Example: severity
|
| sortOrder | string | | The sort order to use when sorting returned alarm definitions. Ascending (ASC) or descending (DESC).
Example: ASC
|
HEADERS
| Key | Datatype | Required | Description |
|---|---|---|---|
opc-request-id | string | Customer part of the request identifier token. If you need to contact Oracle about a particular | |
| request, please provide the complete request ID. | |||
Date | string | (Required) Current Date | |
Authorization | string | (Required) Signature Authentication on Authorization header |
RESPONSES
status: OK
[{"displayName":"Duis commodo","id":"elit ex dolore dolor","severity":"CRITICAL","status":"OK","timestampTriggered":"2014-10-26T06:31:02.895Z","suppression":{"timeSuppressFrom":"1987-07-20T15:37:05.051Z","timeSuppressUntil":"1968-03-29T00:30:10.046Z","description":"deserunt minim esse"}},{"displayName":"ipsum irure","id":"laboris","severity":"CRITICAL","status":"OK","timestampTriggered":"1998-10-11T06:23:01.124Z","suppression":{"timeSuppressFrom":"1997-07-01T12:35:24.780Z","timeSuppressUntil":"2008-02-16T23:07:36.114Z","description":"non minim dolor culpa est"}}]