Diagnosing Composer Problems
Composer provides a "one-click" diagnostics bundle for the Composer platform as part of the Composer Service Monitor.
The diagnostics bundle is primarily useful as an easy way to send Composer the information needed to help you debug a problem. The bundle is a zip file containing all the current log files from all of Composer's microservices. If distributed tracing is enabled and properly configured, the diagnostics bundle may also contain a JSON trace file with the trace ID you specify.
An example of the uncompressed contents of the diagnostic bundle might look like this:
Before you can download the diagnostics bundle, the following conditions must be met:
- Composer and its microservices must be version 3.5 or later.
- All microservices must have service discovery enabled.
- The Composer Service Monitor must be manually installed, configured and started. See Installing and Configuring the Composer Service Monitor.
If you want the diagnostics bundle to include tracing information when a trace ID is specified, the following additional conditions must be met:
- The Composer tracing microservice must be is manually installed, configured and started. See Installing the Composer Tracing Microservice.
- The tracing microservice must have service discovery enabled.
After the Service Monitor is installed, you can download the diagnostics bundle. See Downloading the Diagnostics Bundle.