White Papers

41 REST API Guide  OpenManage Essentials | Revision A02
For example, to get the complete device hierarchy, the following API can be used:
https://<OME_SERVER>:2607/api/OME.svc/DeviceGroupHierarchy
To retrieve device hierarchy information that has changed use a command such as the following:
https://OME_SERVER>:2607/api/OME.svc/DeviceGroupHierarchy/0,0,0,0,0,2,32,205&0,0
,0,0,0,2,32,205&0,0,0,0,0,2,32,204&0,0,0,0,0,2,32,204&0,0,0,0,0,2,32,207&0,0,0,0
,0,2,32,207
2.6 Device Logs
The following resource URI can be used to retrieve the device logs:
<DEVICE_BASE_URI>/<DEVICE_ID>/HWLogs/SEL (to retrieve the SEL logs)
OpenManage Essentials may expose Lifecycle Controller logs in the future and that would require a separate
URI construct as the attributes exposed are slightly different (for example, recommended action and detailed
description).
Operations supported: GET
The attributes associated with each log entry are represented in the following table.
Attribute Name
Description
Severity
The severity of the log message.
Date
The date and time of the message.
Message
The message associated with the HW log entry.
2.7 Alert Filters
OpenManage Essentials alert filters enable the filtering of alerts by severity, time, event category and source,
acknowledged status, and devices/device groups.
The following URI can be used to retrieve all alert filters:
<BASE_URI>/AlertFilters
Operations supported: GET
Attributes (filtering): Id, Type, and IsEnabled
Attributes (sorting): Name Asc (by default)
The attributes associated with an alert filter are described in the following table.