Graphs not loading after proxysql upgrade

Percona Monitoring and Management (PMM) PMM 1.x
1

Proxysql graphs are not loading after upgrading from 1.3.2 to 1.3.5. Here is the error from pmm logs on proxysql server:

level=error msg=“Error scraping for collect.mysql_connection_pool: Error 1045: no such column: Latency_ms” source=“proxysql_exporter.go:204”

PMM version: 1.1.3

Proxysql_error.PNG
Proxysql_error.PNG1910×946 53.8 KB

2

Hi Chanakya , thank you for reporting this issue. This is due to ProxySQL 1.3.5 changing the schema of the stats_mysql_connection_pool table which caused PMM proxysql_exporter to not be able to read any metrics back from ProxySQL. In our upcoming 1.1.4 release (targeting May 25, 2017) we have fixed this issue. In the meantime the workaround is to downgrade to ProxySQL < 1.3.5 .

If you want to keep ProxySQL 1.3.5, you can optionally build the proxysql_exporter from here:
[url]https://github.com/michaelcoburn/proxysql_exporter[/url]

Replace the binary:

sudo mv /usr/local/percona/pmm-client/proxysql_exporter /usr/local/percona/pmm-client/proxysql_exporter.orig
sudo mv ~/proxysql_exporter /usr/local/percona/pmm-client/
sudo chown root:root /usr/local/percona/pmm-client/proxysql_exporter
sudo chmod 755 /usr/local/percona/pmm-client/proxysql_exporter
sudo pmm-admin restart proxysql:metrics

And then update the Latency graph definition PromQL:

proxysql_connection_pool_latency_ms

to

proxysql_connection_pool_latency_us

I hope this helps,

3

Thanks for the info Michael Coburn

4

Hi Michael Coburn , I have upgraded to 1.1.4 but graphs are still the same. Please confirm if this is fixed in this release.

5

Hi Chanakya,

Is pmm-client is also updated to 1.1.4? (not only PMM Server)

can you share versions of pmm-client, PMM Server, ProxySQL and OS?

6

Hi Mykola ,

Graphs came back up after upgrading pmm-client except ‘latency’ graph.
pmm-server: 1.1.4
pmm-client: 1.1.4
OS: Ubuntu 14.04