Exporter MySQL grant requirements changed

Description

PMM-1753 shows as being released in 1.8.0, introducing a change to how MySQL connections are kept open by the mysqld_exporter.

I couldn't find this in the release notes (I tried searching for issue number, "connection" and "scrape"), nor is it made clear on the Managing PMM Client resource.

Since it is best practice to restrict connections for monitoring accounts, this could be causing problems for people. The "recommended" limit from the upstream exporter has always stated 3 connections, which until recently has been working fine for me even with mysql:queries running along side it.

After I upgraded to 1.8.0 I saw an issue with metrics and found:

This occurs for the QAN agent as the mysqld_exporter is holding connections open, which can be seen by monitoring performance_schema.user.

For reference, so far MAX_USER_CONNECTIONS=4 for an account shared between the 2 seems to be fine, although perhaps stating 5 in the documentation would be better.

That said, it appears to be a default of 10 is used if pmm-admin creates the account for you

How to test

None

How to document

None

Activity

Show:

Roma Novikov 
August 2, 2018 at 6:20 PM

I've updated README, to  propose 10 connections as well as we have in Code and in DOC https://www.percona.com/doc/percona-monitoring-and-management/conf-mysql.html#pmm-conf-mysql-user-account-creating  

I can't say: "Everything correct now"  because we not properly tested exporters. We only use them as part of PMM. this can be changed and then we'll pay more attention to exporters and Documentation for them 

 

Michael Coburn 
March 30, 2018 at 6:26 PM

Or we could just change the github readme page to say 10 for our exporter.

https://github.com/percona/mysqld_exporter

do you have a preference?

Done

Details

Assignee

Reporter

Priority

Components

Created March 30, 2018 at 10:24 AM
Updated November 13, 2024 at 9:47 AM
Resolved August 2, 2018 at 6:20 PM