# Proxysql\_exporter error in scraping runtime mysql servers

**URL:** <https://forums.percona.com/t/proxysql-exporter-error-in-scraping-runtime-mysql-servers/35215>\
**Category:** Percona Monitoring and Management (PMM)\
**Created:** [November 23, 2024, 4:35am UTC](https://forums.percona.com/t/proxysql-exporter-error-in-scraping-runtime-mysql-servers/35215 "2024-11-23T04:35:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Animesh\_Agarwal](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/animesh_agarwal/32/9369_2.png) [@Animesh\_Agarwal](https://forums.percona.com/u/Animesh_Agarwal)\
**Post date:** [November 23, 2024, 4:35am UTC](https://forums.percona.com/t/proxysql-exporter-error-in-scraping-runtime-mysql-servers/35215/1 "2024-11-23T04:35:03Z")

</div>

I have deployed pmm-client as a sidecar to the proxysql container. As per the documentation [ProxySQL - Percona Monitoring and Management](https://docs.percona.com/percona-monitoring-and-management/setting-up/client/proxysql.html#usage) we should use admin-stats\_credentials to configure read only user for monitoring process.

I am seeing the below error in the pmm-client container  
`ERRO[2024-11-23T04:08:41.737+00:00] ts=2024-11-23T04:08:41.737Z caller=exporter.go:202 level=error msg="Error scraping for collect.runtime_mysql_servers" agentID=/agent_id/81ed89ee-fa5e-4179-8ebc-f5b0ead063c4 component=agent-process type=proxysql_exporter`

Upon going through the code of proxysql\_exporter [proxysql\_exporter/exporter.go at main · percona/proxysql\_exporter · GitHub](https://github.com/percona/proxysql_exporter/blob/main/exporter.go#L593) it is querying the runtime\_mysql\_servers to which it doesn’t have access as per the documentation [Admin Variables - ProxySQL](https://proxysql.com/documentation/global-variables/admin-variables/#admin-stats_credentials)

Do we need to use admin user with RW permissions? or should we provide additional privileges to the user defined in admin-stats\_credentials

---

<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:** [November 24, 2024, 3:22am UTC](https://forums.percona.com/t/proxysql-exporter-error-in-scraping-runtime-mysql-servers/35215/2 "2024-11-24T03:22:53Z")

</div>

Hello @Animesh_Agarwal,  
That’s a flat out bug. Please report it [https://jira.percona.com/](https://jira.percona.com/) I confirm that our docs say to use the admin-stats\_credential but ProxySQL says that account cannot read any configuration tables. This is probably an oversight in our documentation.

---

<div class="post-metadata">

**Author:** ![vinicius.grippa](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/vinicius.grippa/32/1246_2.png) [@vinicius.grippa](https://forums.percona.com/u/vinicius.grippa)\
**Post date:** [November 9, 2025, 4:25pm UTC](https://forums.percona.com/t/proxysql-exporter-error-in-scraping-runtime-mysql-servers/35215/3 "2025-11-09T16:25:48Z")

</div>

For the record, I opened this JIRA ticket to track this bug:

> **[Jira](https://perconadev.atlassian.net/browse/PMM-14520)**