Logging
Events are entries in the data and event logs. You can access the logs through IAP/MQ and IAP/REST.
IAP/MQ Log Requests and Responses
To issue a log request, a client posts a log request object. And once received, IAP posts the requested log in a log response object.
The log request topic (described in Log Request):
glp/0/{SID}/rq/=logger/client/{CLIENT−ID}/log |
The CMS accumulates the requested records and posts the resulting log response object to (described in Log Response):
glp/0/{SID}/ev/client/{CLIENT−ID}/log |
The IAP log response object echoes the request object, and includes a list of applicable event records.
Live Events
The CMS can report events, as they occur, to the the topics listed below. A typical configuration forwards only error and alarm events as they occur, and logs other diagnostics on request. See Events for more information.
glp/0/{SID}/ev/debug glp/0/{SID}/ev/info glp/0/{SID}/ev/warning glp/0/{SID}/ev/error glp/0/{SID}/ev/data glp/0/{SID}/ev/alarm |
IAP/REST Log Operations
Log Destination
Get the log storage locations. (See Log Destination.)
GET | /iap/log/destination |
Set the storage location for all data and event logs, or for the specified categories. (See Log Destination.)
PUT | /iap/log/destination |
Log Events
Get event entries from the data and event log. (See Log Events.)
GET | /iap/log/ev/{event_id} |
Add an entry to the data and event log. (See Log Events.)
POST | /iap/log/ev |
Update entries in the data and event log. (See Log Events.)
PUT | /iap/log/ev/{event_id} |
Log State
Get the current state for all data and event logs, or for the selected log categories. (See Log State.)
GET | /iap/log/state |
Set the current state for all data and event logs, or for the selected log categories. (See Log State.)
PUT | /iap/log/destination |
Log Status
Get the number of entries and log size for all data and event logs, or for the selected log categories. (See Log Status.)
GET | /iap/log/status |