Hi everyone, A while ago, following the instructions in a forum post, I modified the /etc/collectd.conf file to create a response time graph. It worked well enough for a while, but then it stopped working. Checking the file, I noticed that the customizations I had added were no longer present. I …

CU203 had a correction patch applied for the building of collectd and this then required the collectd files to be shipped, including the default collectd.conf file. If you look through the collectd.conf file you will see that the last line in it is include "/etc/collectd.d/*" which allows you to …

First of all, thank you for your reply. I applied the change you recommended. I moved my configuration to the collectd.custom file, but something probably isn’t working because it stopped working.

I did a test [image] Historical log for WAN latency and performance Network You can also ping other hosts this way. Then in the /etc/collectd.custom file add similar entries as below <Plugin ping> Host "ipfire.org" interval 30 timeout 10 </Plugin> <Plugi…

collectd.custom seems to have a problem with adding the two ping items from the above post. Starting Collection daemon... Parse error in file `/etc/collectd.d/collectd.custom', line 187 near `': syntax error, unexpected $end, expecting EOL yyparse returned error #1 configfile: Cannot read file `/et…

There must be a blank line at the end of the file [Screenshot_20260905-054701_Chrome (1)]

Sorry for the delay in my reply; yes, I made the same mistake too—I had forgotten that a blank line was required.

To be exactly: The line must be terminated by an EOL. :wink: I remember those ‘special’ parser behaviour from long ago with simple compilers. I don’t the EOL is part of the syntax.

External network graph

Community

tphz (iptom) 4 September 2026 15:40 4

I did a test

It looks like it’s still working (for now).

Regards