WIO, IP address is not reported in the chart

Add-Ons
1

IPfire, C203.

[root@ipfire ~]# pakfire status
Core-Version: 2.29-x86_64
Core-Update-Level: 203
Last update: 35d 12h 39m 31s ago
Last core-list update: 7h 25m 14s ago
Last server-list update: 7h 25m 18s ago
Last packages-list update: 7h 25m 14s ago
Core-Update available: no
Package-Updates available: 0
Reboot required: no

[root@ipfire ~]# pakfire info wio
Name: wio
Summary: Who Is Online? IPFire extension
Version: 1.3.2-19
Size: 70.00 KB
Dependencies: 
Pakfile: wio-1.3.2-19.ipfire
Service InitScripts: 
Installed: yes
Status: up-to-date

When WIO checks for hostname, it shows it in the chart (but it doesn’t report what method is used for the test (ping/http/https), this is check with ping for one.one.one.one:

image
image1019×699 35.5 KB

image
image1025×453 29.5 KB

When WIO is configured to check for IP address, than it hides this detail and I see it as a bug:

image
image1017×702 37.4 KB

image
image1029×455 29.1 KB

Dialog for host editing in WIO is missing BACK button. (Compare with DNS service). It should look like this (edited in graphic editor):

image
image1025×453 33.3 KB

Other issue is that WIO hides issues. I reported this issue a long time ago and it was not fixed :frowning:

There was 20 minutes issues on my ISP line few minutes ago, I can see it on hour and day chart but it is not visible on week chart… I see that there was just one issue in the last 24 hours but I cannot tell if similar issue was on the line during the past week or month. I see perfect green rectangle, no sign that there was connectivity problem just few minutes ago:

image
image1026×699 37.6 KB

2

That is a limitation of the time resolution that can be shown on the graphs when the longer time periods are graphed.

3

I still believe it is a bug. There are different aggregation functions available in RRD and I assume that when RRD database is configured in a different way, it will not hide failures on higher resolution. Unfortunately, I am not expert on RRD so I cannot advice how to change RRD configuration to address the issue…

This is current configuration (/var/ipfire/wio/wio.pl):

"DS:mode:GAUGE:3600:0:100",
"RRA:AVERAGE:0.5:1:576",
"RRA:AVERAGE:0.5:6:672",
"RRA:AVERAGE:0.5:24:732",
"RRA:AVERAGE:0.5:144:1460"

It is even possible that this configuration is good but issue is in the function that reads data and creates graph…

Graph is created in /usr/lib/wio/wio-graphs.pl

        my @rrd = ();

        push @rrd, ("-");
        push @rrd, ("--title", "$title");
        push @rrd, ("--start", "-1$period", "-aPNG", "-i", "-z");
        push @rrd, ("--border", "0");
        push @rrd, ("--full-size-mode");
        push @rrd, ("--slope-mode");
        push @rrd, ("--pango-markup");
        push @rrd, ("--alt-y-grid", "-w 910", "-h 300");
        if ( $period eq 'day' ) { push @rrd, ("--x-grid", "MINUTE:30:HOUR:1:HOUR:2:0:%H:%M"); }
        push @rrd, ("--color", "SHADEA".$color{"color19"});
        push @rrd, ("--color", "SHADEB".$color{"color19"});
        push @rrd, ("--color", "BACK".$color{"color21"});
        push @rrd, "DEF:mode=/var/log/rrd/wio/$hostid.rrd:mode:AVERAGE";
        push @rrd, "CDEF:online=mode,UN,0,mode,IF,50,GT,100,0,IF";
        push @rrd, "CDEF:offline=mode,UN,100,mode,IF,50,LT,100,0,IF";
        push @rrd, "AREA:online".$color{"color12"}.":$Lang::tr{'wio up'}\\j";
        push @rrd, "AREA:offline".$color{"color13"}.":$Lang::tr{'wio down'}\\j";
        push @rrd, "-W www.ipfire.org";

        RRDs::graph (@rrd);
4

The original developer of the WIO addon, who supported it for a very long time, stepped back from all IPFire related stuff a couple of years ago.

I am doing my best to support any issues/bugs that get raised with WIO but I am not familiar with the code at all so I have to first figure out how things have been constructed and also decide if the code should be modified to be in line with how things are done in the core IPFire code so there is consistency.

Currently with regard to WIO, there are some other issues related to the update of openvpn to 2.7.x and looking at getting wireguard included in it that will take my attention first as they have been identified several weeks ago.

There is also work ongoing on a replacement for collectd

https://www.ipfire.org/docs/roadmap/telemetry

It probably makes sense to wait for that work to conclude and then see what differences or updates are required to utilise the results of that work.