PMM 2.X agent not collecting SELECT statement

Hi everybody,
nice to “meet” you :slight_smile:

I’m new here and I need your help to solve a strange situation happening in my PMM infrastructure

I deployed a Docker PMM Server and configured 10 client to point to it using perfschema as source for query analytics

I noticed that on some servers (5 of 10) the pmm-agent is not logging SELECT STATEMENT

I initially supposed it could be a server side problem but when i turned on debug level on pmm-agent I saw that the agent is not collecting those kind of statement

This is reflected in the Grafana Dashboard reporting a very different load between my slaves

44% vs 1% depending on it’s collecting or not SELECT

I followed step by step the procedure for deploying clients:
apt update && apt install pmm2-client
pmm-admin config --server-insecure-tls --server-url=https://user:XXX@ipaddr
pmm-admin add mysql --username=pmm --password=XXX --query-source=perfschema

the pmm-admin status is exactly the same on all nodes

I really con’t figure out what is causing the problem

All the servers have the same config (some of them are cloned via xtrabackup and someone are fine and some not)

all other STATEMENT (UPDATE INSERT DELETE) are correctly logged on all clients

I’m running on 2.18 both server and agents

Thanks for your support

Ok … a brief update:

analyzing what the agent is doing i noticed that it queries the events_statements_summary_by_digest table in the performance_schema.

And it’s there that something differs between mysql instances

So the agent is working fine … it’s just the Mysql not doing the same :frowning:

1 Like


truncate table events_statements_summary_by_digest;

Now works like a charm

1 Like

Hi Alfredo,

Thank you for interested in our product.
You are right QAN fetches data from events_statements_summary_by_digest table.
So if some queries are missed than it has to be checked if it were included into this table.