# Bug in ProxySQL dashboard

**URL:** <https://forums.percona.com/t/bug-in-proxysql-dashboard/5654>\
**Category:** PMM 1.x\
**Created:** [June 2, 2017, 8:20am UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654 "2017-06-02T08:20:57Z")\
**Posts on this page:** 1\
**Showing post:** 14

<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:** [July 12, 2017, 8:49am UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/14 "2017-07-12T08:49:26Z")

</div>

[mosi0815](https://percona.vanillacommunities.com/profile/x/x/27342) , well on one hand I am delighted that your environment is again working! But on the other hand I fear that your experience may be the first of several to occur related to discrepancies between status in ProxySQL vs exporter. In my own exploratory testing I was using latest releases:  
[LIST]  
[_]ProxySQL 1.3.7 (Percona build)  
[_]proxysql\_exporter from pmm-client 1.1.5  
[/LIST] I’m going to close this thread, but if you happen to see this issue reoccur please start a new thread and we’ll take action. Thanks again for your cooperation while we diagnosed this!

---

_[View the full topic](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654)._