# I am facing data delay problem on percona PMM dashboard, How to Fix It?

**URL:** <https://forums.percona.com/t/i-am-facing-data-delay-problem-on-percona-pmm-dashboard-how-to-fix-it/18034>\
**Category:** MySQL & MariaDB\
**Tags:** mysql\
**Created:** [October 17, 2022, 8:34am UTC](https://forums.percona.com/t/i-am-facing-data-delay-problem-on-percona-pmm-dashboard-how-to-fix-it/18034 "2022-10-17T08:34:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jahidul.jibon](https://avatars.discourse-cdn.com/v4/letter/j/df788c/32.png) [@jahidul.jibon](https://forums.percona.com/u/jahidul.jibon)\
**Post date:** [October 17, 2022, 8:34am UTC](https://forums.percona.com/t/i-am-facing-data-delay-problem-on-percona-pmm-dashboard-how-to-fix-it/18034/1 "2022-10-17T08:34:28Z")

</div>

I am facing a data delay problem on percona PMM dashboard, We are have data phasing problem.  
in the data phrasing, we cant properly

 ![Screenshot_1](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/f/fee79d155be1f2b5a549126c01114ee3351bde3c.png)  
The below picture can help u find the problem.

server Detaisl:  
Current version: 2.28.0.

---

<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:** [October 17, 2022, 5:23pm UTC](https://forums.percona.com/t/i-am-facing-data-delay-problem-on-percona-pmm-dashboard-how-to-fix-it/18034/2 "2022-10-17T17:23:49Z")

</div>

Check the status of the agent on the server in question. Is it running?

---

<div class="post-metadata">

**Author:** ![jahidul.jibon](https://avatars.discourse-cdn.com/v4/letter/j/df788c/32.png) [@jahidul.jibon](https://forums.percona.com/u/jahidul.jibon)\
**Post date:** [October 18, 2022, 3:41am UTC](https://forums.percona.com/t/i-am-facing-data-delay-problem-on-percona-pmm-dashboard-how-to-fix-it/18034/3 "2022-10-18T03:41:24Z")

</div>

Yes, the agent is running.  
After restarting the agent it seems the same problem.
