v2.6.0

Percona Monitoring and Management 2.6.0

Date:	May 11, 2020
Installation:	Installing Percona Monitoring and Management

Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL, MongoDB, and PostgreSQL performance.

New Features

• PMM-5728: Technical preview of External Services monitoring feature. A new command provides integration with hundreds of third-party systems (https://prometheus.io/docs/instrumenting/exporters/) via the Prometheus protocol so that you can monitor external services on a node where PMM agent is installed.
• PMM-5822: PMM now includes a Security Threat Tool to help users avoid the most common database security issues. Read more here.
• PMM-5559: Global annotations can now be set with the pmm-admin annotate command.
• PMM-4931: PMM now checks Docker environment variables and warns about invalid ones.

Improvements

• PMM-1962: The PMM Server API (via /v1/readyz) now also returns Grafana status information in addition to that for Prometheus.
• PMM-5854: The Service Details dashboards were cleaned up and some unused selectors were removed.
• PMM-5775: It is now clearer which nodes are Primary and which are Secondary on MongoDB Instance dashboards.
• PMM-5549: PMM’s Grafana component is now the latest, 6.7.3.
• PMM-5393: There’s a new ‘Node Summary’ row in the services Summary and Details dashboards summarizing the system update, load average, RAM and memory.
• PMM-4778: mongodb_exporter is now the latest version, 0.11.0.
• PMM-5734: Temporary files activity and utilization charts (rate & irate) were added to the PostgreSQL Instance overview.
• PMM-5695: The error message explains better when using the –-socket option incorrectly.

Bugs Fixed

• PMM-4829: The MongoDB Exporter wasn’t able to collect metrics from hidden nodes without either the latest driver or using the connect-direct parameter.
• PMM-5056: The average values for Query time in the Details and Profile sections were different.
• PMM-2717: Updating MongoDB Exporter resolves an error (Failed to execute find query on 'config.locks': not found.) when used with shardedCluster 3.6.4.
• PMM-4541: MongoDB exporter metrics collection was including system collections from collStats and indexStats, causing “log bloat”.
• PMM-5913: Only totals were shown in QAN when filtering on Cluster=MongoDB.
• PMM-5903: When applying a filter the QAN Overview was being refreshed twice.
• PMM-5821: The Compare button was missing from HA Dashboard main menus.
• PMM-5687: Cumulative charts for Disk Details were not showing any data if metrics were returning NaN results.
• PMM-5663: The ‘version’ value was not being refreshed in various MySQL dashboards.
• PMM-5643: Advanced Data Exploration charts were showing ‘N/A’ for Metric Resolution and ‘No data to show’ in the Metric Data Table.
• PMM-4756: Dashboards were not showing services with empty environments.
• PMM-4562: MongoDB and MySQL registered instances with empty cluster labels (–environment=<label>) were not visible in the dashboard despite being added instances.
• PMM-4906: The MongoDB exporter for MongoDB 4.0 and above was causing a “log bloat” condition.

Help us improve our software quality by reporting any bugs you encounter using our bug tracking system.

v2.5.0

Percona Monitoring and Management 2.5.0

Date:	April 14, 2020
Installation:	Installing Percona Monitoring and Management

Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL, MongoDB, and PostgreSQL performance.

New Features

• PMM-5042 and PMM-5272: PMM can now connect to MySQL instances by specifying a UNIX socket. This can be done with a new --socket option of the pmm-admin add mysql command. (Note: Updates to both PMM Client and PMM Server were done to allow UNIX socket connections.)
• PMM-4145: Amazon RDS instance metrics can now be independently enabled/disabled for Basic and/or Enhanced metrics.

Improvements

• PMM-5581: PMM Server Grafana plugins can now be updated on the command line with the grafana-cli command-line utility.
• PMM-5536: Three Grafana plugins were updated to the latest versions: vertamedia-clickhouse-datasource to 1.9.5, grafana-polystat-panel to 1.1.0, and grafana-piechart-panel to 1.4.0.
• PMM-4252: The resolution of the PMM Server favicon image has been improved.

Bugs Fixed

• PMM-5547: PMM dashboards were failing when presenting data from more than 100 monitored instances (error message proxy error: context canceled).
• PMM-5624: Empty charts were being shown in some Node Temperature dashboards.
• PMM-5637: The Data retention value in Settings was incorrectly showing the value as minutes instead of days.
• PMM-5613: Sorting data by Query Time was not working properly in Query Analytics.
• PMM-5554: Totals in charts were inconsistently plotted with different colors across charts.
• PMM-4919: The force option (--force) in pmm-admin config was not always working.
• PMM-5351: The documentation on MongoDB user privileges has been corrected.

Help us improve our software quality by reporting any bugs you encounter using our bug tracking system.

v2.4.0

Percona Monitoring and Management 2.4.0

Date:	March 18, 2020
Installation:	Installing Percona Monitoring and Management

Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL, MongoDB, and PostgreSQL performance.

New Features

• PMM-3387: Prometheus custom configuration is now supported by PMM Server. The feature is targeted at experienced users and is done by adding the base configuration file into the PMM Server container to be parsed and included into the managed Prometheus configuration.
• PMM-5186: Including –-pprof option in the pmm-admin summary command adds pprof debug profiles to the diagnostics data archive
• PMM-5102: The new “Node Details” dashboard now displays data from the hardware monitoring sensors in hwmon. The new dashboard is based on the hwmon collector data from the node_exporter. Please note that data may be unavailable for some nodes because of the configuration or virtualization parameters.

Improvements

• PMM-4915: The Query Analytics dashboard now shows Time Metrics in the Profile Section as “AVG per query” instead of “AVG per second”

• PMM-5470: ClickHouse query optimized for Query Analytics to improve its speed and reduce the load on the back-end

• PMM-5448: The default high and medium metrics resolutions were changed to 1-5-30 and 5-10-60 sec. To reduce the effect of this change on existing installations, systems having the “old” high resolution chosen on the PMM Settings page (5-5-60 sec.) will be automatically re-configured to the medium one during an upgrade. If the resolution was changed to some custom values via API, it will not be affected

• PMM-5531: A health check indicator was implemented for the PMM Server Docker image. It is based on the Docker HEALTHCHECK. This feature can be used as follows:

  docker inspect -f {% raw %}{{.State.Health.Status}}{% endraw %}
  until [ "`docker inspect -f {% raw %}{{.State.Health.Status}}{% endraw %} pmm-server`" == "healthy" ]; do sleep 1; done

• PMM-5489: The “Total” line in all charts is now drawn with the same red color for better consistency

• PMM-5461: Memory graphs on the node-related dashboards were adjusted to have fixed colors that are more distinguishable from each other

• PMM-5329: Prometheus in PMM Server was updated to version 2.16.0. This update has brought several improvements. Among them are significantly reduced memory footprint of the loaded TSDB blocks, lower memory footprint for the compaction process (caused by the more balanced choice of what to buffer during compaction), and improved query performance for the queries that only touch the most recent 2 hours of data.

• PMM-5210: Data Retention is now specified in days instead of seconds on the PMM Settings page. Please note this is a UI-only change, so the actual data retention precision is not changed

• PMM-5182: The logs.zip archive available on the PMM Settings page now includes additional self-monitoring information in a separate client subfolder. This subfolder contains information collected on the PMM Server and is equivalent to the one collected on a node by the pmm-admin summary command.

• PMM-5112: The Inventory API List requests now can be filtered by the Node/Service/Agent type

Bugs Fixed

• PMM-5178: Query Detail Section of the Query Analytics dashboard didn’t show tables definitions and indexes for the internal PostgreSQL database
• PMM-5465: MySQL Instance related dashboards had row names not always matching the actual contents. To fix this, elements were re-ordered and additional rows were added for better matching of the row name and the corresponding elements
• PMM-5455: Dashboards from the Insight menu were fixed to work correctly when the low resolution is set on the PMM Settings page
• PMM-5446: A number of the Compare Dashboards were fixed to work correctly when the low resolution is set on the PMM Settings page
• PMM-5430: MySQL Exporter section on the Prometheus Exporter Status dashboard now collapsed by default to be consistent with other database-related sections
• PMM-5445, PMM-5439, PMM-5427, PMM-5426, PMM-5419: Labels change (which occurs e.g. when the metrics resolution is changed on the PMM Settings page) was breaking dashboards
• PMM-5347: Selecting queries on the Query Analytics dashboard was generating errors in the browser console
• PMM-5305: Some applied filters on the Query Analytics dashboard were not preserved after changing the time range
• PMM-5267: The Refresh button was not working on the Query Analytics dashboard
• PMM-5003: pmm-admin list and status use different JSON naming for the same data
• PMM-5526: A typo was fixed in the Replication Dashboard description tooltip

Help us improve our software quality by reporting any bugs you encounter using our bug tracking system.

v2.3.0

Percona Monitoring and Management 2.3.0

Date:	February 19, 2020

Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL, MongoDB, and PostgreSQL performance.

For PMM install instructions, see Installing PMM Server and Installing PMM Client.

⚠️ Caution
PMM 2 is designed to be used as a new installation — please don’t try to upgrade your existing PMM 1 environment.

Improvements and new features

• PMM-5064 and PMM-5065: Starting from this release, users will be able to integrate PMM with an external Alertmanager by specifying the Alertmanager URL and the Alert Rules to be executed inside the PMM server (This feature is for advanced users only at this point)
• PMM-4954: Query Analytics dashboard now shows units both in the list of queries in a summary table and in the Details section to ease understanding of the presented data
• PMM-5179: Relations between metrics are now specified in the Query Analytics Details section
• PMM-5115: The CPU frequency and temperature graphs were added to the CPU Utilization dashboard
• PMM-5394: A special treatment for the node-related dashboards was implemented for the situations when the data resolution change causes new metrics to be generated for existing nodes and services, to make graphs show continuous lines of the same colors

Fixed bugs

• PMM-4620: The high CPU usage by the pmm-agent process related to MongoDB Query Analytics was fixed
• PMM-5377: singlestats showing percentage had sparklines scaled vertically along with the graph swing, which made it difficult to visually notice the difference between neighboring singlestats.
• PMM-5204: Changing resolution on the PMM settings page was breaking some singlestats on the Home and MySQL Overview dashboards
• PMM-5251: Vertical scroll bars on the graph elements were not allowed to do a full scroll, making last rows of the legend unavailable for some graphs
• PMM-5410: The “Available Downtime before SST Required” chart on the PXC/Galera Node Summary dashboard was not showing data because it was unable to use metrics available with different scraping intervals

v2.2.1

Percona Monitoring and Management 2.2.1

Date:	January 23, 2020

Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL, MongoDB, and PostgreSQL performance.

For PMM install instructions, see Installing PMM Server and Installing PMM Client.

⚠️ Caution
PMM 2 is designed to be used as a new installation — please don’t try to upgrade your existing PMM 1 environment.

PMM Server version 2.2.0 suffered an unauthenticated denial of service vulnerability (CVE-2020-7920). Any other PMM versions do not carry the same code logic, and are thus unaffected by this issue. Users who have already deployed PMM Server 2.2.0 are advised to upgrade to version 2.2.1 which resolves this issue.

Improvements and new features

• PMM-5229: The new RDS Exporter section added to the Prometheus Exporter Status dashboard shows singlestats and charts related to the rds_exporter
• PMM-5228 and PMM-5238: The Prometheus dashboard and the Exporters Overview dashboard were updated to include the rds_exporter metrics in their charts, allowing better understanding of the impacts of monitoring RDS instances
• PMM-4830: The consistency of the applied filters between the Query Analytics and the Overview dashboards was implemented, and now filters selected in QAN will continue to be active after the switch to any of the Overview dashboards available in the Services menu
• PMM-5235: The DB uptime singlestats in node rows on the Home dashboard were changed to show minimal values instead of average ones to be consistent with the top row
• PMM-5127: The “Search by” bar on the Query Analytics dashboard was renamed to “Filter by” to make its purpose more clear
• PMM-5131: The Filter panel on the Query Analytics dashboard now shows the total number of available Labels within the “See all” link, which appears if the Filter panel section shows only top 5 of its Labels

Fixed bugs

• PMM-5232: The pmm-managed component of the PMM Server 2.2.0 is vulnerable to DoS attacks, that could be carried out by anyone who knows the PMM Server IP address (CVE-2020-7920). Versions other than 2.2.0 are not affected.
• PMM-5226: The handlebars package was updated to version 4.5.3 because of the Prototype Pollution vulnerability in it (CVE-2019-19919). Please note PMM versions were not affected by this vulnerability, as handlebars package is used as a build dependency only.
• PMM-5206: Switching to the Settings dashboard was breaking the visual style of some elements on the Home dashboard
• PMM-5139: The breadcrumb panel, which shows all dashboards visited within one session starting from the root, was unable to fully show breadcrumb longer than one line
• PMM-5212: The explanatory text was added to the Download PMM Server Logs button in the Diagnostic section of the PMM Settings dashboard, and a link to it was added to the Prometheus dashboard which was the previous place to download logs
• PMM-5215: The unneeded mariadb-libs package was removed from the PMM Server 2.2.0 OVF image, resulting in both faster updating with the yum update command and avoiding dependency conflict messages in the update logs
• PMM-5216: PMM Server Upgrade to 2.2.0 was showing Grafana Update Error page with the Refresh button which had to be clicked to start using the updated version
• PMM-5211: The “Where do I get the security credentials for my Amazon RDS DB instance” link in the Add AWS RDS MySQL or Aurora MySQL instance dialog was not targeted at the appropriate instruction
• PMM-5217: PMM 2.x OVF Image memory size was increased from 1 Gb to 4 Gb with the additional 1 Gb swap space because the previous amount was hardly housing the PMM Server, and it wasn’t enough in some cases like performing an upgrade
• PMM-5271: LVM logical volumes were wrongly resized on AWS deployment, resulting in “no space left on device” errors
• PMM-5295: InnoDB Transaction Rollback Rate values on the MySQL InnoDB Details dashboard were calculated incorrectly
• PMM-5270: PXC/Galera Cluster Summary dashboard was showing empty Cluster drop-down list, making it impossible to choose the cluster name
• PMM-4769: The wrongly named “Timeout value used for retransmitting” singlestat on the Network Details dashboard was renamed to “The algorithm used to determine the timeout value” and updated to show the algorithm name instead of a digital code
• PMM-5260: Extensive resource consumption by pmm-agent took place in case of Query Analytics for PostgreSQL; it was fixed by a number of optimizations in the code, resulting in about 4 times smaller memory usage
• PMM-5261: CPU usage charts on all dashboards which contain them have undergone colors update to make softIRQ and Steal curves better differentiated
• PMM-5244: High memory consumption in the PMM Server with a large number of agents sending data simultaneously was fixed by improving bulk data insertion to the ClickHouse database

v2.2.0

Percona Monitoring and Management 2.2.0

Date:	December 24, 2019

Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL, MongoDB, and PostgreSQL performance. You can run PMM in your own environment for maximum security and reliability. It provides thorough time-based analysis for MySQL, MongoDB, and PostgreSQL servers to ensure that your data works as efficiently as possible.

Main improvements in this release are:

• Alternative installation methods available for PMM 1.x are re-implemented for PMM 2: now PMM Server can be installed as a virtual appliance, or run using AWS Marketplace
• AWS RDS and remote instances monitoring re-added in this release include AWS RDS MySQL / Aurora MySQL instances, and remote PostgreSQL, MySQL, MongoDB, and ProxySQL ones
• The new Settings dashboard allows configuring PMM Server via the graphical interface

For PMM install instructions, see Installing PMM Server and Installing PMM Client.

⚠️ Caution
PMM 2 is designed to be used as a new installation — please don’t try to upgrade your existing PMM 1 environment.

Improvements and new features

• PMM-4575: The new PMM Settings dashboard allows users to configure various PMM Server options: setting metrics resolution and data retention, enabling or disabling send usage data statistics back to Percona and checking for updates; this dashboard is now the proper place to upload your public key for the SSH login and to download PMM Server logs for diagnostics
• PMM-4907 and PMM-4767: The user’s AMI Instance ID is now used to setup running PMM Server using AWS Marketplace as an additional verification on the user, based on the Amazon Marketplace rules
• PMM-4950 and PMM-3094: Alternative AWS partitions are now supported when adding an AWS RDS MySQL or Aurora MySQL Instance to PMM
• PMM-4976: Home dashboard clean-up: “Systems under monitoring” and “Network IO” singlestats were refined to be based on the host variable; also avoiding using color as an indicator of state; “All” row elements were relinked to the “Nodes Overview” dashboard with regards to the selected host.
• PMM-4800: The pmm-admin add mysql command has been modified to make help text more descriptive: now when you enable tablestats you will get more detail on if they’re enabled for your environment and where you stand with respect to the auto-disable limit
• PMM-4969: Update Grafana to version 6.5.1
• PMM-5053: A tooltip was added to the Head Block graph on the Prometheus dashboard
• PMM-5068: Drill-down links were added to the Node Summary dashboard graphs
• PMM-5050: Drill-down links were added to the graphs on all Services Compare dashboards
• PMM-5037: Drill-down links were added to all graphs on the Services Overview dashboards
• PMM-4988: Filtering in Query Analytics have undergone improvements to make group selection more intuitive: Labels unavailable under the current selection are shown as gray/disabled, and the percentage values are dynamically recalculated to reflect Labels available within the currently applied filters
• PMM-4966: All passwords are now substituted with asterisk signs in the exporter logs for security reasons when not in debug mode
• PMM-527: node_exporter is now providing hardware monitoring information such as CPU temperatures and fan statuses; while this information is being collected by PMM Server, it will not be shown until a dedicated dashboard is added in a future release
• PMM-3198: Instead of showing All graphs for all services by default, MySQL Command/Handler Counters Compare dashboard now shows the predefined set of ten most informative ones, to reduce load on PMM Server at its first open

Fixed bugs

• PMM-4978: The “Top MySQL Questions” singlestat on the MySQL Instances Overview dashboard was changed to show ops instead of percentage
• PMM-4917: The “Systems under monitoring” and “Monitored DB Instances” singlestats on the Home dashboard now have a sparkline to make situation more clear with recently shut down nodes/instances
• PMM-4979: Set decimal precision 2 for all the elements, including charts and singlestats, on all dashboards
• PMM-4980: Fix “Load Average” singlestat on the Node Summary dashboard to show decimal value instead of percent
• PMM-4981: Disable automatic color gradient in filled graphs on all dashboards
• PMM-4941: Some charts were incorrectly showing empty fragments with high time resolution turned on
• PMM-5022: Fix outdated drill-down links on the Prometheus Exporters Overview and Nodes Overview dashboards
• PMM-5023: Make the All instances uptime singlestat on the Home dashboard to show Min values instead of Avg
• PMM-5029: Option to upload dashboard snapshot to Percona was disappearing after upgrade to 2.1.x
• PMM-4946: Rename singlestats on the Home dashboard for better clarity: “Systems under monitoring” to “Nodes under monitoring” and “Monitored DB Instances” to “Monitored DB Services”, and make the last one to count remote DB instances also
• PMM-5015: Fix format of Disk Page Buffers singlestat on the Compare dashboard for PostgreSQL to have two digits precision for the consistency with other singlestats
• PMM-5014: LVM logical volumes were wrongly sized on a new AWS deployment, resulting in “no space left on device” errors.
• PMM-4804: Incorrect parameters validation required both service-name and service-id parameters of the pmm-admin remove command to be presented, while the command itself demanded only one of them to identify the service.
• PMM-3298: Panic errors were present in the rds_exporter log after adding an RDS instance from the second AWS account
• PMM-5089: The serialize-javascript package was updated to version 2.1.1 because of the possibility of regular expressions cross-site scripting vulnerability in it (CVE-2019-16769). Please note PMM versions were not affected by this vulnerability, as serialize-javascript package is used as a build dependency only.
• PMM-5149: Disk Space singlestat was unable to show data for RDS instances because of not taking into account sources with unknown file system type

v2.1.0

Percona Monitoring and Management 2.1.0

Date:	November 11, 2019

Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL, MongoDB, and PostgreSQL performance. You can run PMM in your own environment for maximum security and reliability. It provides thorough time-based analysis for MySQL, MongoDB, and PostgreSQL servers to ensure that your data works as efficiently as possible.

For install instructions, see Installing Percona Monitoring and Management.

⚠️ Caution
PMM 2 is designed to be used as a new installation — please don’t try to upgrade your existing PMM 1 environment.

Improvements and new features

• PMM-4063: Update QAN filter panel to show only labels available for selection under currently applied filters
• PMM-815: Latency Detail graph added to the MongoDB Instance Summary dashboard
• PMM-4768: Disable heavy-load collectors automatically when there are too many tables
• PMM-4821: Use color gradient in filled graphs on all dashboards
• PMM-4733: Add more log and configuration files to the downloadable logs.zip archive
• PMM-4672: Use integer percentage values in QAN filter panel
• PMM-4857: Update tooltips for all MongoDB dashboards
• PMM-4616: Rename column in the Query Details section in QAN from Total to Sum
• PMM-4770: Use Go 1.12.10
• PMM-4780: Update Grafana to version 6.4.1
• PMM-4918: Update Grafana plugins to newer versions, including the clickhouse-datasource plugin

Fixed bugs

• PMM-4935: Wrong instance name displayed on the MySQL Instance Summary dashboard due to the incorrect string crop
• PMM-4916: Wrong values are shown when changing the time range for the Node Summary Dashboard in case of remote instances
• PMM-4895 and PMM-4814: The update process reports completion before it is actually done and therefore some dashboards, etc. may not be updated
• PMM-4876: PMM Server access credentials are shown by the pmm-admin status command instead of hiding them for security reasons
• PMM-4875: PostgreSQL error log gets flooded with warnings when pg_stat_statements extension is not installed in the database used by PMM Server or when PostgreSQL user is unable to connect to it
• PMM-4852: Node name has an incorrect value if the Home dashboard opened after QAN
• PMM-4847: Drill-downs from the Environment Overview dashboard doesn’t show data for the preselected host
• PMM-4841 and PMM-4845: pg_stat_statement QAN Agent leaks database connections
• PMM-4831: Clean-up representation of selectors names on MySQL-related dashboards for a better consistency
• PMM-4824: Incorrectly calculated singlestat values on MySQL Instances Overview dashboard
• PMM-4819: In case of the only one monitored host, its uptime is shown as a smaller value than the all hosts uptime due to the inaccurate rounding
• PMM-4816: Set equal thresholds to avoid confusing singlestat color differences on a Home dashboard
• PMM-4718: Labels are not fully displayed in the filter panel of the Query Details section in QAN
• PMM-4545: Long queries are not fully visible in the Query Examples section in QAN

Help us improve our software quality by reporting any Percona Monitoring and Management bugs you encounter using our bug tracking system.

v2.0.1

Percona Monitoring and Management 2.0.1

Date:	October 9, 2019

Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL, MongoDB, and PostgreSQL performance. You can run PMM in your own environment for maximum security and reliability. It provides thorough time-based analysis for MySQL, MongoDB, and PostgreSQL servers to ensure that your data works as efficiently as possible.

For install instructions, see Installing Percona Monitoring and Management.

⚠️ Caution
PMM 2 is designed to be used as a new installation — please don’t try to upgrade your existing PMM 1 environment.

Improvements

• PMM-4779: Securely share dashboards with Percona
• PMM-4735: Keep one old slowlog file after rotation
• PMM-4724: Alt+click on check updates button enables force-update
• PMM-4444: Return “what’s new” URL with the information extracted from the pmm-update package change log

Fixed bugs

• PMM-4758: Remove Inventory rows from dashboards
• PMM-4757: qan_mysql_perfschema_agent failed querying events_statements_summary_by_digest due to data types conversion
• PMM-4755: Fixed a typo in the InnoDB AHI Miss Ratio formula
• PMM-4749: Navigation from Dashboards to QAN when some Node or Service was selected now applies filtering by them in QAN
• PMM-4742: General information links were updated to go to PMM 2 related pages
• PMM-4739: Remove request instances list
• PMM-4734: A fix was made for the collecting node_name formula at MySQL Replication Summary dashboard
• PMM-4729: Fixes were made for formulas on MySQL Instances Overview
• PMM-4726: Links to services in MongoDB singlestats didn’t show Node name
• PMM-4720: machine_id could contain trailing \\n
• PMM-4640: It was not possible to add MongoDB remotely if password contained a # symbol

Help us improve our software quality by reporting any Percona Monitoring and Management bugs you encounter using our bug tracking system.

v2.0.0

Percona Monitoring and Management 2.0.0

Date:	September 19, 2019

Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL, MongoDB, and PostgreSQL performance. You can run PMM in your own environment for the best security and reliability. It provides thorough time-based analysis for MySQL, MongoDB, and PostgreSQL servers to ensure that your data works as efficiently as possible.

For install instructions, see Installing Percona Monitoring and Management.

⚠️ Caution
PMM 2 is designed to be used as a new installation — please don’t try to upgrade your existing PMM 1 environment.

The new PMM2 introduces a number of enhancements and additional feature improvements, including:

• Detailed query analytics and filtering technologies which enable you to identify issues faster than ever before.
• A better user experience: Service-level dashboards give you immediate access to the data you need.
• The new addition of PostgreSQL query tuning.
• Enhanced security protocols to ensure your data is safe.
• Our new API allows you to extend and interact with third-party tools.

More details about new and improved features available within the release can be found in the corresponding blog post.

Help us improve our software quality by reporting any Percona Monitoring and Management bugs you encounter using our bug tracking system.