Schedule demo

List Alarms V3 API


This API will list all alarms of the monitors configured in the Applications Manager for the user corresponding to the provided API Key. The response includes details such as Monitor Details, Severity, Alert Triggered Time, Alert Message, Assigned Technician, Latest Annotation, and Attribute Details for each Alert. Additionally, specific alerts can be filtered by Severity, Monitor Group, Custom Field, Type, or category by including appropriate filters in the request.

Note: The allowed roles include Administrator, Operator and User.

Example API Request:

https://apm-prod-server:8443/api/v3/alarms

Request Parameters

FieldDescriptionPossible values
acknowledgedTo show/hide acknowledged alerts.True/False
attributeIdTo show the alerts of a particular attribute(s).ID of the attribute.
attributeTypeTo filter only health, availability or attribute level alert(s).Health, Availability, and others.
(Multiple values can be entered separated by commas)
categoryTo filter monitors that come under a selected resource group.SER, NET, SYS, URL, MS, APP, DBS, CAM, MOM, ERP, NWD, SAN, VIR, CLD, EMO, and CIF.
customFieldNameTo filter the result set assigned to a particular custom field.Name of the custom field.
customFieldTypeTo filter the result set assigned to a particular custom field type.Type of the custom field (Only 'list' is supported for now).
customFieldValueTo filter the result set assigned to a particular custom field value.Value of the custom field.
durationTo filter alerts that are triggered during the given duration.
  • hH - Last 30 minutes
  • H - Last 1 hour
  • H3 - Last 3 hours
  • H6 - Last 6 hours
  • hD - Last 12 hours
  • D - Last 24 hours
  • SD - Today
  • ID - Yesterday
  • W - Last 7 days
  • M - Last 30 days
endTimeTo filter alerts triggered before a given time.Time in milliseconds (Eg: endTime=1248868798900)
includeSubLevelTo include sub level alerts.True/False
monitorGroupTo show the alerts of a particular monitor group(s).Name of the Monitor Group(s).
(Multiple values can be entered separated by commas)
monitorGroupIdTo show the alerts of a particular monitor group ID(s).ID of the Monitor Group(s).
(Multiple values can be entered separated by commas)
monitorNameTo show the alerts of a particular monitor(s).Name of the Monitor(s).
(Multiple values can be entered separated by commas)
onlyMonitorsTo include only monitor alerts. It excludes all monitor group alerts.True/False
onlyMonitorGroupsTo include only monitor group alerts. It excludes all monitor level alerts.True/False
pageTo determine the page to be returned.Numeric value
resourceIdTo show the alerts of a particular resource ID(s).Resource ID of the Monitor(s)/Monitor Group(s).
(Multiple values can be entered separated by commas)
rowsTo determine the number of rows to be returned to the selected page.Number of rows to be returned.
severityTo filter the result set based on the severity value.Critical/Warning/Clear/Down/Up
sortByColumnTo sort the result set based on the column provided.Monitorname/Severity/Modifiedtime
sortByTypeTo sort the results in ascending/descending order.ASC/DESC
startTimeTo filter alerts triggered after a given time.Time in milliseconds (Eg: startTime=1248868798900)
typeTo filter monitors that belong to a particular monitor type(s).Name of the Monitor type.
(Multiple values can be entered separated by commas)
viewTo determine the response template.Basic/Extended
 
Key points:
  • On providing the attributeId, the attributeType parameter should not be included.
  • On providing the monitorName/resourceId, the parameters for type, category, onlyMonitors, onlyMonitorGroups, custom field, resourceId, and monitor group should not be included.
  • On providing the monitorGroup/monitorGroupId, the parameters for monitorGroup, custom field, monitorName, and resourceId should not be included.
  • Users may provide either the type or category parameter, but not both simultaneously.
  • Users may provide either the duration or startTime/endTime, but not both simultaneously.
  • Either OnlyMonitors or OnlyMonitorGroups should be set to true, but not both.
  • All three parameters, customFieldName, customFieldValue, and customFieldType, are required when applying the Custom Field filter.
  • The value of startTime should be less than that of the endTime.

Sample Request

Listing recent alarms within a certain time range

https://apm-prod-server:8443/api/v3/alarms?startTime=1248868798412&endTime=1248868798900

Listing monitor level Health and Availability alarms

https://apm-prod-server:8443/api/v3/alarms?attributeType=health,availability&onlyMonitors=true

Response Parameters

FieldDescription        
Alarm Details
resourceIdResource ID of the Monitor
displayNameDisplay name of the Monitor
monitorTypeThe type of monitor
monitorTypeDisplayNameDisplay name of the monitor type
parentResourceIdResource id of the parent monitor
parentMonitorNameName of the parent monitor
parentMonitorTypeType of the parent monitor
severitySeverity value in integer form (Possible values: Down/Critical - 1, Warning - 4, Up/Clear - 5)
severityTextSeverity in I18N text
alertCreationTimeTime alert was created (in ms)
alertModifiedTimeInMillisAlert modification time (in ms)
alertModifiedTimeAlert modification time in word format
prettyTimeTime since the alert is triggered
messageAlert message
technicianName of the user assigned to the alert
attributeIdAttribute id of the alert
attributeNameAttribute name of the alert
attributeDisplayNameAttribute display name of the alert
annotationAddedIndicates whether the alert has an annotation or not (Possible values: true/false)
latestNoteLatest annotation
managedServerNameName of the Probe Server of the monitor (Only for Central Server )

Example Response

{
"message": "success",
"data": [
{
"displayName": "Production_Tomcat-server",
"monitorTypeDisplayName": "Tomcat Server",
"parentMonitorName": "",
"parentMonitorType": "",
"severityText": "Critical",
"alertCreationTime": "Apr 25, 2024 3:58 PM",
"alertModifiedTime": "Apr 30, 2024 1:56 PM",
"prettyTime": "2d 2h 55min 21s ago.",
"message": "Health of Production_Tomcat-server (Tomcat-server) is critical. <br>Root
Cause : <br>1. Heap Memory (MemoryUsage) --> Used Memory in MB 316 > 0 (threshold).<br>",
"technician": "",
"attributeDisplayName": "Health",
"annotationAdded": false,
"latestNote": "",
"managedServerName": ""
},
{
"displayName": "Production_Tomcat-server",
"monitorTypeDisplayName": "Tomcat Server",
"parentMonitorName": "",
"parentMonitorType": "",
"severityText": "Up",
"alertCreationTime": "Apr 25, 2024 3:56 PM",
"alertModifiedTime": "Apr 25, 2024 3:56 PM",
"prettyTime": "7d 55min 5s ago.",
"message": "Resource up. <br>The resource Production_Tomcat-server is available.",
"technician": "",
"attributeDisplayName": "Availability",
"annotationAdded": false,
"latestNote": "",
"managedServerName": ""
}
],
"meta": {
"total": 2,
"records": 2,
"page": 1
}
}

Loved by customers all over the world

"Standout Tool With Extensive Monitoring Capabilities"

It allows us to track crucial metrics such as response times, resource utilization, error rates, and transaction performance. The real-time monitoring alerts promptly notify us of any issues or anomalies, enabling us to take immediate action.

Reviewer Role: Research and Development

carlos-rivero
"I like Applications Manager because it helps us to detect issues present in our servers and SQL databases."
Carlos Rivero

Tech Support Manager, Lexmark

Trusted by over 6000+ businesses globally