Service Audit Logging
Service audit logging provides data about flow and coded (for example, Java) services that run in Integration Server. You can use service log entries and data to do the following:
Track when services start, their status, and their duration.
Track whether services completed successfully or failed.
Record the client that called the service, and the
Integration Server port on which the client connected.
Resubmit services.
In Integration Server, you globally disable all logging for all services, globally enable one type of logging for all services, or enable customized logging on a service-by-service basis. If you enable customized logging, you set up the customized logging for specific services in Designer. For each service, you can choose the following:
When to log based on how the service is called. For example, you might choose to log only when the service is called by a client request or trigger, as opposed to by other services.
On what status to log. For example, you might choose to log only when the service fails.
Whether to store the service’s input pipeline and, if so, when. For example, you might choose to log the input pipeline only when an error occurs. Storing the input pipeline allows you to resubmit the service later if necessary.
Note:
Whether you enable or disable service logging in Integration Server and Designer, if error logging is enabled, Integration Server always writes error log entries when service errors occur. The data includes stack trace data about the errors.
You can augment service logging data using Integration Server built-in services. The built-in services do the following:
Enable services to post user-defined progress messages to the
Integration Server server log or the IS Core Audit Log. For example, you might have a service post messages to indicate that certain pieces of code ran successfully, or to record run-time values for variables so you can see how the values changed as the service ran.
Enable services to write the pipeline to the
Integration Server server log.