# Too many system events in QAN while monitoring Aurora MySQL

**URL:** <https://forums.percona.com/t/too-many-system-events-in-qan-while-monitoring-aurora-mysql/7075>\
**Category:** PMM 1.x\
**Created:** [June 21, 2019, 9:56pm UTC](https://forums.percona.com/t/too-many-system-events-in-qan-while-monitoring-aurora-mysql/7075 "2019-06-21T21:56:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmorton](https://avatars.discourse-cdn.com/v4/letter/b/50afbb/32.png) [@bmorton](https://forums.percona.com/u/bmorton)\
**Post date:** [June 21, 2019, 9:56pm UTC](https://forums.percona.com/t/too-many-system-events-in-qan-while-monitoring-aurora-mysql/7075/1 "2019-06-21T21:56:45Z")

</div>

I’ve used PMM to monitor Percona XtraDB and MySQL instances before with little trouble. This is my first time using it to monitor Aurora MySQL. In QAN, I mostly see system events such as heartbeat and performance\_schema queries. This happens until the performance\_schema.events\_statements\_summary\_by\_digest table is full. According to AWS support, the size of this table cannot be increased on Aurora.

My question is, how do I “filter” the events logged in performance\_schema to only show queries against user schemas?