Composer Monitoring Solution
Composer system metrics are published by all Composer microservices. While these measurements provide some visibility of the operating state of the services, the metric data becomes more useful once it can be stored and viewed. In order to provide Composer deployments with observability into the health and performance of the running system, you can use a monitoring solution. This topic describes an example monitoring solution that we make available for download with each release of Composer.
Monitoring Solution Components
The monitoring solution consists of several components that are built up as layers.
Generic operating and Composer specific metrics form the fixed foundation layer and are published in various formats.
Subsequent layers provide storage and visualisation capabilities to support further analysis.
Subsequent components added to the metrics foundation can be implemented as provided in the monitoring solution package, or you can substitute them with preferred components that were already deployed.
The example solution is built using the following industry-standard, open-source tools:
Prometheus service collects and stores metrics in a time series database.
Grafana supports further analysis by providing visualisation of stored metrics on pre-built application-specific dashboards.
We provide these components in a tarball containing docker-compose files. We include the configuration files required for monitoring Composer services, along with ready to use dashboards.
Contact your Composer Customer Support representative to download the Solution Package: Customer Support.
When you get the tarball, extract the tarball to the directory you create.
tar -xvf composer-monitoring-X.Y.Z.tar.gz -C composer-monitoring
Open the READ.me file and follow the directions included.