Logging in the Red Hat® OpenShift® Container Platform
Some FTM offerings have components that are based on Liberty that is deployed in containerized environments.
The following table shows the various types of logs in FTM deployments.
| Log type | Location | Details |
|---|---|---|
| Application execution logs | ||
| FTM system logs | Database | These logs are shown in the Control Center user interface System Logs section. They are the same logs that go to the container console. |
| Liberty logs | ||
| Java™ Platform, Enterprise Edition message logs | Container console | The consoleSource attribute in the Liberty
server.xml file controls what goes into the container console. By default it is same as
contents of messages.log. |
| Java Platform, Enterprise Edition trace logs | Container console | These logs are level 2 logs, which might not be needed for everyday operations. |
| Java Platform, Enterprise Edition FFDC logs | Container console | Java Platform, Enterprise Edition Liberty FFDC logs are written inside the container. These logs are level 2 logs, which might not be needed for everyday operations. FFDC logs are created on failure incidents. |
| Java Platform, Standard Edition logs | ||
| Java Platform, Standard Edition console logs | Container console | Human readable logs generated by Java Platform, Standard Edition components. Available as container console logs. |
| IBM® MQ and IBM App Connect logs | ||
| IBM MQ logs | Container console | Console output of the runmqserver and strmqweb commands. |
| IBM App Connect logs | Container console | Console output of the runaceserver command. |
| FTM level 2 trace logs | Persistent volume - pv-ftm-ace-logs |
For more information about the instrumentation and trace logs, see Instrumentation and trace. |