Column | Description |
Date/Time | Date and time the audit record was written to the database or file system. |
Audit time stamp | Date and time the entry was written to the log. |
Service name | Service that generated the audit event. |
Status | Current status of the service (Started, Retried, Ended, or Failed). |
Duration | Length of time the service ran (in milliseconds). |
Error message | If the service failed, message that describes the error that occurred. |
Server ID | Integration Server on which the service that generated the log entry ran. This is necessary information when Integration Servers are clustered and writing to a shared RDBMS. The ID can be DNSname:port or IPaddress:port. Note: The port is always the Integration Server’s primary port, even if a service executed on a different (non‑primary) Integration Server port. |
User ID | Integration Server user name of the client that called the service that generated the log entry. |
Resubmittable | Whether you can resubmit the service from Monitor. You can resubmit a service if it is a top-level (as opposed to nested) service and the service’s input pipeline was logged. |
Client ID | IP address of the host from which the request originated. |
Pipeline flag | Whether the service log includes a copy of the input pipeline. |
System data flag | Whether system data is available. |
Audited parent ID | Context ID of the next higher service in the call stack that was audited. |
Client application | Client application accessing the server. If this is an OAuth related request and the request has an access_token, this holds the client_id to which the token was issued. |
Root Context Parent Context Current Context | Context information Monitor uses to connect related entries from different logs. |