Capture log information

Application logs that are written to the local file system are not always persisted on cloud platforms. Generally, logs should be directed to the process console (stdout/stderr) so the cloud platform can manage them without configuration for finding specific log files.

In the IBM Cloud public Kubernetes or Cloud Foundry environments, logs can be forwarded to the IBM Log Analysis with LogDNA service.

Application logs for servers running on Red Hat OpenShift Container Platform can be forwarded to the Elasticsearch / Fluentd / Kibana log analysis facility.

Liberty can be configured to emit logs, trace, System.err, System.out, FFDC, and HTTP access logs in JSON format to the console for consumption by downstream log analysis.

Similarly, WebSphere Application Server traditional running in Docker containers can log in JSON format to emit logs, trace, System.out, and System.err to the console for downstream log analysis.

This rule flags Java code that has references to the following packages:

For more information, see Analyzing application Logs on Red Hat OpenShift Container Platform with Elasticsearch, Fluentd, and Kibana.