# Table statistics dashboard and "Top Tables by rows read"

**URL:** <https://forums.percona.com/t/table-statistics-dashboard-and-top-tables-by-rows-read/6638>\
**Category:** PMM 1.x\
**Created:** [October 18, 2018, 10:38am UTC](https://forums.percona.com/t/table-statistics-dashboard-and-top-tables-by-rows-read/6638 "2018-10-18T10:38:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MickMc](https://avatars.discourse-cdn.com/v4/letter/m/d2c977/32.png) [@MickMc](https://forums.percona.com/u/MickMc)\
**Post date:** [October 18, 2018, 10:38am UTC](https://forums.percona.com/t/table-statistics-dashboard-and-top-tables-by-rows-read/6638/1 "2018-10-18T10:38:15Z")

</div>

Hello,  
In the “Top tables by rows read” dashboard, reads from performance\_schema.events\_statements\_history appears to constantly increase over time until PMM is restarted (see attached screenshot, although this applies to all of our monitored instances). I’m guessing this is an error with the way the metric is collected, rather than an accurate statistic. can you please confirm?  
Edit: I should add that we use performance\_schema as a source for query analytics, in case that makes a difference  
Cheers

 ![photoid=52690](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/1/1f792c538690303b1f5d85a767ca2ffc7246e013.png)

---

<div class="post-metadata">

**Author:** ![Michael\_Coburn](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_coburn/32/18_2.png) [@Michael\_Coburn](https://forums.percona.com/u/Michael_Coburn)\
**Post date:** [October 22, 2018, 1:04pm UTC](https://forums.percona.com/t/table-statistics-dashboard-and-top-tables-by-rows-read/6638/2 "2018-10-22T13:04:05Z")

</div>

Hi [MickMc](https://percona.vanillacommunities.com/profile/x/x/42415)

That’s correct, it is due to fetching results from

```auto
PERFORMANCE_SCHEMA.events_statements_history

```

that is done by qan-agent (Query Analytics). This shouldn’t be an error.  
[url][qan-agent/worker.go at 744504971772163e451fd0f4289e160b72d58c17 · percona/qan-agent · GitHub](https://github.com/percona/qan-agent/blob/744504971772163e451fd0f4289e160b72d58c17/qan/analyzer/mysql/worker/perfschema/worker.go#L370%5B/url%5D)

You can evaluate the impact by stopping mysql:queries on one node and observe the line should flatten.

```auto
pmm-admin stop mysql:queries

```