# Slow log as query source but still get expensive perfschema queries

**URL:** https://forums.percona.com/t/slow-log-as-query-source-but-still-get-expensive-perfschema-queries/35625
**Category:** PMM 2.x
**Created:** [December 12, 2024, 9:52am UTC](https://forums.percona.com/t/slow-log-as-query-source-but-still-get-expensive-perfschema-queries/35625 "2024-12-12T09:52:44Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Davesson](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/davesson/32/16955_2.png) [@Davesson](https://forums.percona.com/u/Davesson)
#### Post date: [December 12, 2024, 9:52am UTC](https://forums.percona.com/t/slow-log-as-query-source-but-still-get-expensive-perfschema-queries/35625/1 "2024-12-12T09:52:44Z")

</div>

## Description:

I’ve added a mysql server with slowlog as query source:

```auto
pmm-admin add mysql --query-source=slowlog --size-slow-logs=1GiB --disable-tablestats=true --username=pmm --password=xxxxxx mysql-0 10.0.10.10:3306

```

Can still see these expensive perfschema queries running by the pmm mysql user

```auto
select event_name, count_star, sum_timer_wait from performance_schema.events_waits_summary_global_by_event_name

select event_name, count_read, sum_timer_read, sum_number_of_bytes_read, count_write, sum_timer_write, sum_number_of_bytes_write, count_misc, sum_timer_misc from performance_schema.file_summary_by_event_name

```

Did I miss something? I’ve tried removing the server and adding it again

## Version:

ProjectName: pmm-admin  
Version: 2.42.0  
PMMVersion: 2.42.0  
Timestamp: 2024-06-06 15:28:26 (UTC)  
FullCommit: 74e57527735bd062c4bd37adbd89c31bb14ebc15

---

<div class="post-metadata">

### Author: ![lalit.choudhary](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lalit.choudhary/32/51_2.png) [@lalit.choudhary](https://forums.percona.com/u/lalit.choudhary)
#### Post date: [December 13, 2024, 5:59am UTC](https://forums.percona.com/t/slow-log-as-query-source-but-still-get-expensive-perfschema-queries/35625/2 "2024-12-13T05:59:47Z")

</div>

Hello @Davesson,

I can see the same behavior in my test.

The `--query-source` option applies to the QAN dashboard. It specifies where to get the query details for QAN. But for other dashboards, PMM uses system tables like performance\_schema to get information on events, locking, replication etc. Because of this, we still see queries running on performance\_schema.

---

<div class="post-metadata">

### Author: ![lalit.choudhary](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lalit.choudhary/32/51_2.png) [@lalit.choudhary](https://forums.percona.com/u/lalit.choudhary)
#### Post date: [December 13, 2024, 10:19am UTC](https://forums.percona.com/t/slow-log-as-query-source-but-still-get-expensive-perfschema-queries/35625/3 "2024-12-13T10:19:01Z")

</div>

Hello @Davesson  
Regarding expensive performence\_schema queries, if you see performance issues due to them, please report them to our bug database with full details.  
[https://perconadev.atlassian.net](https://perconadev.atlassian.net)