# All beats have missing documents or timestamp not accurate
**URL:** https://discuss.elastic.co/t/all-beats-have-missing-documents-or-timestamp-not-accurate/295065
**Category:** Beats
**Tags:** filebeat, packetbeat, metricbeat, heartbeat, auditbeat
**Created:** [January 21, 2022, 2:27pm UTC](https://discuss.elastic.co/t/all-beats-have-missing-documents-or-timestamp-not-accurate/295065 "2022-01-21T14:27:02Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@cctk](https://discuss.elastic.co/u/cctk)
#### Post date: [January 21, 2022, 2:27pm UTC](https://discuss.elastic.co/t/all-beats-have-missing-documents-or-timestamp-not-accurate/295065/1 "2022-01-21T14:27:02Z")
I am experiencing several documents missing after the upgrade to 7.0. Metricbeat dashboard used to show a regular update of the cpu and memory , however now it now shows a dash (-) for 1m before showing update. this makes it very difficult to track the health of the servers.
is there any way to go back to how it was before to prevent showing no units. (picture below shows explanation )
I can't create proper watchers and keep track of when the cpu is high or in danger like this.
---
### Author:  [@lucasfcosta](https://discuss.elastic.co/u/lucasfcosta)
#### Post date: [January 24, 2022, 9:07am UTC](https://discuss.elastic.co/t/all-beats-have-missing-documents-or-timestamp-not-accurate/295065/3 "2022-01-24T09:07:48Z")
Hi @cctk, thanks for contacting us.
Just to be sure, I assume these dashboards were created using the `metricbeat setup` command, is that correct?
Could you also double check the logs for your beats to see if they're facing any errors and double check the clock on your servers?
One more thing to try would be to run a query using the Kibana console under the Dev Tools to see the raw documents themselves, so that you can see the field's names and values and compare that to the queries used by your dashboard.
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [January 24, 2022, 2:52pm UTC](https://discuss.elastic.co/t/all-beats-have-missing-documents-or-timestamp-not-accurate/295065/4 "2022-01-24T14:52:27Z")
Which version are you on? Are you on 7.0 or 7.16?
---
### Author:  [@cctk](https://discuss.elastic.co/u/cctk)
#### Post date: [January 25, 2022, 9:27am UTC](https://discuss.elastic.co/t/all-beats-have-missing-documents-or-timestamp-not-accurate/295065/5 "2022-01-25T09:27:34Z")
7.15.1
---
### Author:  [@cctk](https://discuss.elastic.co/u/cctk)
#### Post date: [January 25, 2022, 10:10am UTC](https://discuss.elastic.co/t/all-beats-have-missing-documents-or-timestamp-not-accurate/295065/6 "2022-01-25T10:10:47Z")
Yes I used `metricbeat setup` command.
I get this part but no error
```auto
fetching V2 controller: []string{" *****"} for pid 5465
```
I get the above command for awhile before I get normal logs again. where its collecting the metrics.
no errors in log file.
the clock on my server is in UTC
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [January 25, 2022, 2:30pm UTC](https://discuss.elastic.co/t/all-beats-have-missing-documents-or-timestamp-not-accurate/295065/7 "2022-01-25T14:30:56Z")
The issue here is probably one of the following:
1. Some incompatibility between a 6.x and a 7.x dashboard
2. Some issue where not all documents are indexed
If you're certain that docs are missing from _all_ beats that points to 2, esp. since heartbeat doesn't have a dashboard.
Can you verify which beats you're actively using? @lucasfcosta and I are heartbeat experts, but if this is mostly a metricbeat issue you'll want to speak to a metricbeat expert.
---
### Author:  [@cctk](https://discuss.elastic.co/u/cctk)
#### Post date: [January 26, 2022, 1:38pm UTC](https://discuss.elastic.co/t/all-beats-have-missing-documents-or-timestamp-not-accurate/295065/8 "2022-01-26T13:38:51Z")
I have fixed the issue with the metricbeat dashboard thank you.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 23, 2022, 3:39pm UTC](https://discuss.elastic.co/t/all-beats-have-missing-documents-or-timestamp-not-accurate/295065/9 "2022-02-23T15:39:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.