Monitor 10.11 | pub.monitor.service Folder | pub.monitor.service:getActivityLogs
 
pub.monitor.service:getActivityLogs
Retrieves all user-defined messages that were logged for a specified service or all services that are descendants of the specified service.
Input Parameters
The following table lists the input parameters.
contextID
String Context ID for the service whose user-defined messages you want to retrieve. Specify the complete, exact ID.
Note:
Whether Monitor treats contextID as case-sensitive depends on how the underlying database (for example, Oracle, DB2, or SQL server) handles the queries that Monitor issues to obtain data.
Output Parameters
The following table lists the output parameters.
activityLogs
Document List List of the retrieved messages. For each user-defined message, the following fields are returned:
*ROOTCONTEXTID String Context ID of the service's root service. If the service is a top-level service, the root context ID is the same as the context ID.
*PARENTCONTEXTID String Context ID of the service's parent service if the service was nested or resubmitted.
*CONTEXTID String Context ID for the service.
*ENTRYTYPE String The type of user-defined message, that is error, warning, or message.
*BRIEFMESSAGE String A brief version of the text of the message that contains only up to 240 characters.
*FULLMESSAGE String The text of the user-defined message. It will contain up to 1024 characters.
*B2BUSER String Integration Server user name of the client that invoked the service.
*SERVERID String DNS name and port of the Integration Server that ran the service (for example, titanium.east.webmethods.com:5555).
*AUDITTIMESTAMP Number Time the message was logged, in epoch time; that is, the number of seconds since January 1, 1970.
*AUDITTIMESTRING String Time the message was logged in string format, YYYY-MM-DD hh:mm:ss.SSS zzz, where:
*YYYY-MM-DD is the date
*hh:mm:ss:SSS is the time, including milliseconds
*zzz is the time zone