# "update every" seems to be ignored

**URL:** <https://community.netdata.cloud/t/update-every-seems-to-be-ignored/4754>\
**Category:** Help\
**Tags:** configuration, agent\
**Created:** [October 15, 2023, 11:57am UTC](https://community.netdata.cloud/t/update-every-seems-to-be-ignored/4754 "2023-10-15T11:57:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Carlos\_Jesus](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/carlos_jesus/32/2692_2.png) [@Carlos\_Jesus](https://community.netdata.cloud/u/Carlos_Jesus)\
**Post date:** [October 15, 2023, 11:57am UTC](https://community.netdata.cloud/t/update-every-seems-to-be-ignored/4754/1 "2023-10-15T11:57:41Z")

</div>

Hello!  
I’m locally monitoring 7 machines in a 1 parent - 6 Childs configuration. 4 of them are bare metal, the rest proxmox VMs. 1 ubuntu Lunar, all other debian bookworm/bullseye. All running latest buil (currently v1.42.0-361-nightly)  
I’ve set in all 7 machines

[db]  
update every = 2

but charts still get updated every second (with new values) instead of 2 seconds. I’ve tried also setting

[global statistics]  
update every = 2

even though I believe it shouldn’t be necessary.

I’ve configured according to:

> **[Install Netdata with kickstart.sh | Learn Netdata](https://learn.netdata.cloud/docs/netdata-agent/installation/linux)**
>
> The kickstart.sh script installs Netdata from source, including all dependencies required to connect to Netdata Cloud, with a single command.

and

> **[Configuring Metrics Centralization Points | Learn Netdata](https://learn.netdata.cloud/docs/netdata-parents/metrics-centralization-points/configuring-metrics-centralization-points)**
>
> What You'll Learn

It seems simple enough and everything works perfectly except for this small detail. I’m sure I’ve overlooked something but cant really put my finger on it.

My (sanitized) stream.conf are:  
#Child node  
[stream]  
enabled = yes  
destination = 192.XXX.XXX.XXX  
api key = XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX  
timeout seconds = 60  
default port = 19999  
send charts matching = \*  
buffer size bytes = 1048576  
reconnect delay seconds = 5  
initial clock resync iterations = 60

#parent node

# [API\_KEY] is [YOUR-API-KEY], i.e [11111111-2222-3333-4444-555555555555]

[XXXXXXX-XXXX-XXXX-XXX-XXXXXX]  
enabled = yes  
enable compression = yes  
allow from = \*  
default memory mode = dbengine  
health enabled by default = auto  
default postpone alarms on connect seconds = 60  
multiple connections = allow

Any help is appreciated,  
Best regards,  
CJ

---

<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:** [October 15, 2023, 2:51pm UTC](https://community.netdata.cloud/t/update-every-seems-to-be-ignored/4754/2 "2023-10-15T14:51:33Z")

</div>

Hi, @Carlos_Jesus. It is not ignored, regardless of the value of “update\_every” the charts are always updated every second. But the data is collected every “update\_every”. If you check the chart values, you will notice that they changed every “update\_every”.

---

<div class="post-metadata">

**Author:** ![Carlos\_Jesus](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/carlos_jesus/32/2692_2.png) [@Carlos\_Jesus](https://community.netdata.cloud/u/Carlos_Jesus)\
**Post date:** [October 15, 2023, 3:52pm UTC](https://community.netdata.cloud/t/update-every-seems-to-be-ignored/4754/3 "2023-10-15T15:52:49Z")

</div>

Yes. It is true.

 ![Untitled](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/2X/c/ccb7679a16c1eae6194799d6efb183a25aaec5cf.png)  
I was misslead by the chart refresh, and the view point average.  
Granularity is indeed correct. the “1 second point” in between updates are linear interpolations.

Thanks for your help and sorry for the noise…

best regards