Impact of Changing Data Collection Interval in OpenWISP2

1 view
Skip to first unread message

Logunath K

unread,
Sep 29, 2025, 1:24:02 AM (4 days ago) Sep 29
to open...@googlegroups.com

Dear Team,

                    I wanted to inform you about the behavior of charts when modifying the data collection interval in OpenWISP2.

Currently, the interval is set to 300 seconds (5 minutes), which means the agent sends data to the server every 5 minutes. If we change this value to 900 seconds (15 minutes) or any other value.

“What will be the behavior of the charts if I select a 1-day view, since the chart data will be displayed at 10-minute intervals?”

Thanks in advance

Regards,

logu

Federico Capoano

unread,
Sep 29, 2025, 1:13:24 PM (4 days ago) Sep 29
to open...@googlegroups.com
Charts use fixed intervals based on the selected time range (for 1-day it’s 10 minutes).  

Changing the agent interval doesn’t change this, so with a 15-minute interval for data collection, you may end up with a chart with missing bars, the only way to find out is to try.
If that happens and you don't want to have missing bars, you could either lower the interval to 10 minutes, or monkeypatch the code to change this line:


I recently shared on Github Discussions a solution to monkey-patch the DeviceAdmin class to modify the columns listed in the device list:

You can adapt that solution and change the ready() method to do something like:

AbstractChart.GROUP_MAP["1d"] = "15m"

You may want to ask yourself if it makes sense to have a monitoring system that gets updates every 15 minutes, which in many deployments could be considered a long time.
However, it may work for you, so if you think that's the case, you can adapt the system.

I think we cannot ship a default setup that suits everyone, but we should definitely make it possible to change the existing behavior whenever possible.

I hope this helps.

Best regards
Federico Capoano


--
You received this message because you are subscribed to the Google Groups "OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openwisp+u...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/openwisp/CAJy2ivrN3OuBy2_11VgNmEV_Up9cGL9ftefEXbh7aGcm%2BoiStg%40mail.gmail.com.

Logunath K

unread,
Sep 30, 2025, 12:59:18 AM (3 days ago) Sep 30
to open...@googlegroups.com
Thank you for sharing this detailed explanation — it’s very useful. I’ll start checking this on my side.

At the same time, I just want to confirm one point: if I increase the agent interval from 5 minutes to 15 minutes, this would also affect the application of templates/ping/config_applied, correct? Means templates/ping/config_applied would only be applied after 15 minutes instead of 5 minutes.

if I change the run_checks schedule in Celery like this: 
'run_checks': { 'task': 'openwisp_monitoring.check.tasks.run_checks', 'schedule': timedelta(minutes=5), -> Here If I change 5min to 15mins. },

Please confirm if my understanding is correct.


Regards,
logu

Federico Capoano

unread,
Sep 30, 2025, 9:14:34 AM (3 days ago) Sep 30
to open...@googlegroups.com
There's 3 intervals:

- openwisp-config agent interval, in /etc/config/openwisp on OpenWrt
- openwisp-monitoring agent interval, in /etc/config/openwisp-monitoring on OpenWrt (passive metric collection)
- run_checks interval (active metric collection), in the settings.py on the server

If you want everything to run every 15 minutes you have to change all of them.
Reply all
Reply to author
Forward
0 new messages