Preparing for logging and monitoring
Content services containers provide logging and monitoring capabilities for troubleshooting, performance monitoring, and capacity planning based on monitoring data in real production environments.
About this task
To simplify the enablement of these capabilities, the logging and monitoring components are built into each container product image. You can start using monitoring and logging capabilities very easily by providing a few required environment variables and volumes.
With the logging capability, you can ingest the system log, the Liberty log, and product logs into the back-end logging service that you choose.
With the monitoring capability, you can collect system metrics like CPU, memory, IO, and network data that is related to the content services products through the PCH monitor plug-in, and Liberty runtime information through the JMX plug-in.
- IBM Cloud® logging and monitoring service
- Open source Elasticsearch, Logstash, and Kibana (ELK) stack for logging service, and Graphite/Grafana/Carbon for monitoring service
This information helps you to create and collect the settings you need to enable the containers' logging and monitoring capabilities at deployment time.
When you prepare your environment, record the settings so that these values are available to enter into the IBM Business Automation Configuration Container tool, or into the jobs.yml file for deployment and configuration. For lists of the parameters that you need to collect, see the following section: Content services parameters.