Contribute in GitHub: |

Logging and Auditing

The IBM® Security Verify Directory Integrator containers, by default, send all auditing and logging information to the console of the container in JSON format.

Logging

By default all error and informational messages for the IBM® Security Verify Directory Integrator containers are logged to the console of the container in JSON format. A standard message contains the following fields.

Field	Description
instance.epochSecond	The number of seconds since Unix epoch at which the message was generated.
instance.nanoOfSecond	The number of nanoseconds since the epochSecond at which the message was generated.
instance.thread	The name of the thread that generated the message.
instance.threadId	The identifier of the thread that generated the message.
instance.priority	The priority of the thread that generated the message.
instance.level	The level of the generated message (for example, `INFO`).
instance.loggerName	The name of the component that generated the message (for example, `ISVDI Bootstrapper`).
instance.message	The text that is associated with the generated message.
instance.endOfBatch	The EndOfBatch status of the logging event, as "true" or "false".
instance.loggerFqcn	The fully qualified common name of the component that generated the message (for example, `com.ibm.sdi.bootstrapper`).

An example message is:

{
  "instant":{
     "epochSecond":1694062572,
     "nanoOfSecond":741919939
  },
  "thread":"/mnt/host/BasicAL.xml",
  "threadId":29,
  "threadPriority":5,
  "level":"INFO",
  "loggerName":"com.ibm.di.config.interfaces.MetamergeConfigFactory",
  "message":"CTGDKE011I Reviewing namespace /mnt/host/BasicAL.xml for garbage collection.",
  "endOfBatch":false,
  "loggerFqcn":"org.apache.logging.log4j.spi.AbstractLogger"
}

Note: To make the example more readable, the JSON is formatted across multiple lines. In a containerized environment, the JSON message is collapsed into a single line.

The general.logging.json-logging Boolean configuration entry, when set to false, disables the JSON based logging, and changes the message format to a simple text string.

The general.logging.root-level and general.logging.loggers configuration entries control the amount of logging that is generated by the server. For more information, see YAML Specification.