Percona announces the release of Percona Monitoring and Management 1.4.0.
This release introduces the support of external Prometheus exporters so that you can create dashboards in the Metrics monitor even for the monitoring services other than those provided with PMM client packages. To attach an existing external Prometheus exporter, run
pmm-admin add external:metrics NAME_OF_EXPORTER URL:PORT.
The list of attached monitoring services is now available not only in the tabular format but also as a JSON file to enable automatic verification of your configuration. To view the list of monitoring services in the JSON format run
pmm-admin list --json.
In this release, Prometheus and Grafana have been upgraded. Prometheus version 1.7.2, shipped with this release, offers a number of bug fixes that will contribute to its smooth operation inside PMM. For more information, see the Prometheus change log.
Version 4.5.2 of Grafana, included in this release of PMM, offers a number of new tools that will facilitate data analysis in PMM:
query editorfor Prometheus expressions features syntax highlighting and autocompletion for metrics, functions and range vectors.
Query inspectorprovides detailed information about the query. The primary goal of graph inspector is to enable analyzing a graph which does not display data as expected.
The complete list of new features in Graphana 4.5.0 is available from What’s New in Grafana v4.5.
For install and upgrade instructions, see Deploying Percona Monitoring and Management.
- PMM-1520: Prometheus upgraded to version 1.7.2.
- PMM-1521: Grafana upgraded to version 4.5.2.
- PMM-1091: The
pmm-admin listproduces a JSON document as output if the
--jsonoption is supplied.
- PMM-507: External exporters are supported with pmm-admin.
- PMM-1622: docker images of PMM Server are available for downloading as tar packages.
- PMM-1553: Consul upgraded to the 0.8 release.
- PMM-1172: In some cases, the
TABLESsection of a query in QAN could contain no data and display the List of tables is empty error. The
Explainsections had the relevant values.
- PMM-1519: A Prometheus instance could be forced to shut down if it contained too many targets (more than 50). When started the next time, Prometheus initiated a time-consuming crash recovery routine which took long on large installations.