# Unable to obtain continuous perf data

**URL:** https://community.netdata.cloud/t/unable-to-obtain-continuous-perf-data/2382
**Category:** Help
**Tags:** agent-collector, agent, agent-configuration
**Created:** [January 6, 2022, 2:29am UTC](https://community.netdata.cloud/t/unable-to-obtain-continuous-perf-data/2382 "2022-01-06T02:29:08Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![wtkhysm5](https://avatars.discourse-cdn.com/v4/letter/w/b4bc9f/32.png) [@wtkhysm5](https://community.netdata.cloud/u/wtkhysm5)
#### Post date: [January 6, 2022, 2:29am UTC](https://community.netdata.cloud/t/unable-to-obtain-continuous-perf-data/2382/1 "2022-01-06T02:29:08Z")

</div>

## Environment

OS：CentOS-7.6-4.14.0-115.el7a.0.1.aarch64  
Netdata：v1.31.0-242-gb0b0fbd

## Problem/Question

I use the perf.plugins and want to collect all the data every second. It works very well when I do nothing. But when I run some big large programs and CPU fully loaded, it seems netdata can not get continuous data. Cannot see continuous lines but intermittent line on the dashboard. ( I want to upload the photo of dashboard here but always fail. )  
I get this in error.log.

```auto
2022-01-05 18:13:34: netdata ERROR : PLUGIN[proc] : heartbeat missed 6790000 monotonic microseconds
2022-01-05 18:13:40: netdata ERROR : PLUGIN[proc] : heartbeat missed 4090000 monotonic microseconds
2022-01-05 18:13:43: netdata ERROR : PLUGIN[proc] : heartbeat missed 1890000 monotonic microseconds
2022-01-05 18:13:43: perf.plugin ERROR : MAIN : heartbeat missed 6980000 monotonic microseconds
2022-01-05 18:13:44: netdata ERROR : MAIN : EXPORTING: '150.1.68.201:10121' closed the socket
2022-01-05 18:13:50: perf.plugin ERROR : MAIN : heartbeat missed 6000000 monotonic microseconds
2022-01-05 18:13:52: netdata ERROR : PLUGIN[proc] : heartbeat missed 8010000 monotonic microseconds
2022-01-05 18:13:57: netdata ERROR : PLUGIN[proc] : heartbeat missed 3990000 monotonic microseconds
2022-01-05 18:13:58: netdata ERROR : MAIN : EXPORTING: '150.1.68.201:10121' closed the socket
2022-01-05 18:13:59: perf.plugin ERROR : MAIN : heartbeat missed 7610000 monotonic microseconds
2022-01-05 18:14:05: perf.plugin ERROR : MAIN : heartbeat missed 4650000 monotonic microseconds
2022-01-05 18:14:06: netdata ERROR : PLUGIN[proc] : heartbeat missed 8070000 monotonic microseconds

```

By the way, I already set netdata.conf.

> [global]  
> process scheduling policy = rr  
> process scheduling priority = 99

## What I expected to happen

So how can I solve this problem?  
Thanks.

---

<div class="post-metadata">

### Author: ![vlvkobal](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/vlvkobal/32/219_2.png) [@vlvkobal](https://community.netdata.cloud/u/vlvkobal)
#### Post date: [January 11, 2022, 11:16am UTC](https://community.netdata.cloud/t/unable-to-obtain-continuous-perf-data/2382/2 "2022-01-11T11:16:24Z")

</div>

Do you see gaps in all the charts or just for the perf plugin?

---

<div class="post-metadata">

### Author: ![wtkhysm5](https://avatars.discourse-cdn.com/v4/letter/w/b4bc9f/32.png) [@wtkhysm5](https://community.netdata.cloud/u/wtkhysm5)
#### Post date: [January 13, 2022, 1:23am UTC](https://community.netdata.cloud/t/unable-to-obtain-continuous-perf-data/2382/3 "2022-01-13T01:23:43Z")

</div>

Yes, I see gaps in all the charts.  
I change the priority of netdata in netdata.conf, it didn’t work. But I change the priority in netdata.service, it works.  
Thanks for your reply.

---

<div class="post-metadata">

### Author: ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)
#### Post date: [January 18, 2022, 5:33pm UTC](https://community.netdata.cloud/t/unable-to-obtain-continuous-perf-data/2382/4 "2022-01-18T17:33:46Z")

</div>

Here is the [link to the GitHub issue](https://github.com/netdata/netdata/issues/11938).

> [@wtkhysm5](#):
>
> I change the priority of netdata in netdata.conf, it didn’t work. But I change the priority in netdata.service, it works.

As we discussed on GitHub: it is expected behavior and is [documented](https://learn.netdata.cloud/docs/agent/daemon#scheduling-settings-and-systemd).

I brought up this topic internally and we discussed it within the team, we decided to keep the settings as they are.
