Logger configurations in OCP

In current customer there is a need to modify the OOTB log formatter delivered with RHPAM images:

<formatter name="COLOR-PATTERN">
        <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} ${env.VSAD_ID} %-5p [%c] (%t) %s%e%n"/>
</formatter>

Notice the addition of `${enf.VSAD_ID}` to add a placeholder for an environment variable that identifies internally in the organization the log origin, this is picked up by the log analysis tools that discriminate the logs per application in the organization.

We are currently solving the customer need by modifying the OOTB standalone-openshift.xml, adding the formatter that we are required by the customer.

This approach some times leads to miss-configurations, specially when the standalone-openshift.xml suffer changes from one EAP version to the other in the blessed image by Red Hat.

As an enhancement here I suggest to add environment variables to the image that can enable the creation of formatters.

Additional to this, multiple times, support requires to add some DEBUG log level to a given class; enabling that in openshift also requires the creation of a logger line:

<logger category="org.interesting.class.for.support">
  <level name="DEBUG"/>
</logger>

This is currently challenging in OCP, as we might need to add the logger using jboss-cli and restarting the EAP service, which some times leads to health check exceptions that could destroy the pod in the process, challenging the debugging for the given class.

Adding DEBUG level to some classes also helps the development of processes where some classes like custom work item handlers, event listeners or custom utilities play an important role in the functionality.

Adding a method for adding DEBUG level to some classes can be also useful.