# Missing NEW MySQL Schema in PMM

**URL:** <https://forums.percona.com/t/missing-new-mysql-schema-in-pmm/29113>\
**Category:** Percona Monitoring and Management (PMM)\
**Tags:** pmm, mysql\
**Created:** [March 13, 2024, 2:20pm UTC](https://forums.percona.com/t/missing-new-mysql-schema-in-pmm/29113 "2024-03-13T14:20:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Deon\_Joubert1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/deon_joubert1/32/3659_2.png) [@Deon\_Joubert1](https://forums.percona.com/u/Deon_Joubert1)\
**Post date:** [March 13, 2024, 2:20pm UTC](https://forums.percona.com/t/missing-new-mysql-schema-in-pmm/29113/1 "2024-03-13T14:20:46Z")

</div>

## Description:

A new schema that was created on a MySQL does not show up in PMM Query Analytics. The new schema, called **data\_2024** , is used all the time by the clients, so I really expect a lot of queries to show up on it. I’ve set up the agent to monitor `perfschema`.

## Tried So Far

I’ve restarted the pmm agent on the host, but am not in a position to restart the MySQL service unless absolutely necessary. (and I don’t know that it will solve the problem)

## Version:

- We’re running PMM Server 2.41.0.
- I’ve got pmm-admin version is 2.19.0
- All of this is running on SUSE Linux Enterprise Server 12 SP3
- Kernel 4.4.73-5-default
- 5.7.24-log MySQL Community Server (GPL)

## Expected Result:

I expect to see queries from all schemas on the MySQL host to be listed under query analytics. I also expect all the schemas (including **data\_2024** ) to show up in the filter panel on the left of query analytics.

Further, the usernames of clients connected to the MySQL host aren’t listed in the filter panel either.

## Actual Result:

“data\_2024” is nowhere to be found in the filter panel or any actual queries in the query analyzer. I’ve checked `SQL_TEXT` in the performance\_schema tables and can find queries with "data\_2024’, so, I really expect them to show up in PMM query analytics.

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [March 14, 2024, 2:00am UTC](https://forums.percona.com/t/missing-new-mysql-schema-in-pmm/29113/2 "2024-03-14T02:00:31Z")

</div>

Did you configure the PMM agent to collect from slow log or performance\_schema? You can use `pmm-admin list` to verify which collector is running.

---

<div class="post-metadata">

**Author:** ![Deon\_Joubert1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/deon_joubert1/32/3659_2.png) [@Deon\_Joubert1](https://forums.percona.com/u/Deon_Joubert1)\
**Post date:** [March 14, 2024, 5:28am UTC](https://forums.percona.com/t/missing-new-mysql-schema-in-pmm/29113/3 "2024-03-14T05:28:56Z")

</div>

> [@Deon\_Joubert1](#):
>
> I’ve set up the agent to monitor `perfschem`

Hi @matthewb , thanks for responding. Yes, as I’ve mentioned in the description section, I’ve configured it to monitor `perfschema`:

```auto
Service type Service name Address and port Service ID
MySQL b-fleetdbhyper-mysql 127.0.0.1:3306 /service_id/8d357e76-972b-4532-9c28-1898138ee634

Agent type Status Metrics Mode Agent ID Service ID
pmm_agent Connected /agent_id/f046ebea-aa76-4c58-98e5-16cbe2e499b8
node_exporter Running push /agent_id/25e019ea-cb4b-41e2-ad1a-b609af1ebbe6
mysqld_exporter Running push /agent_id/9529d38b-a980-4b3d-8656-2e30b920b224 /service_id/8d357e76-972b-4532-9c28-1898138ee634
mysql_perfschema_agent Running /agent_id/85198c2a-8712-4fd0-926f-f14646395087 /service_id/8d357e76-972b-4532-9c28-1898138ee634
vmagent Running push /agent_id/db5143bc-501a-4980-b07e-03d4647e9b16

```

---

<div class="post-metadata">

**Author:** ![Deon\_Joubert1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/deon_joubert1/32/3659_2.png) [@Deon\_Joubert1](https://forums.percona.com/u/Deon_Joubert1)\
**Post date:** [March 14, 2024, 8:22am UTC](https://forums.percona.com/t/missing-new-mysql-schema-in-pmm/29113/4 "2024-03-14T08:22:05Z")

</div>

I have restarted our READ-ONLY REPLICA (which also did not show up with **data\_2024** queries) server. That means **mysqld** and the **pmm agent** was restarted.

After the restart, searching for “data\_2024” shows queries from that schema, but it still isn’t listed as a schema in the filter panel.

_ **Q: Is it expected behaviour for new schemas not to show up in query analytics until restarts?** _