Skip to Content.
Sympa Menu

rare-users - Re: [RARE-users] [rare-dev] SNMP for monitoring RTT, jitter and packet loss with freeRouter

Subject: RARE user and assistance email list

List archive

Re: [RARE-users] [rare-dev] SNMP for monitoring RTT, jitter and packet loss with freeRouter


Chronological Thread 
  • From: Frédéric LOUI <>
  • To:
  • Cc:
  • Subject: Re: [RARE-users] [rare-dev] SNMP for monitoring RTT, jitter and packet loss with freeRouter
  • Date: Mon, 10 Apr 2023 11:07:51 +0200
  • Dkim-filter: OpenDKIM Filter v2.10.3 zmtaauth04.partage.renater.fr A1EC21C0097

Hi Gabriel,

> I am wanting to monitor some specific data regarding the network interfaces
> of freeRouter,
> mainly RTT, jitter and packet loss of the interfaces would be interesting
> data for me.
OK

> freeRouter? I saw that for prometheus there is no specific sensor for this
> interface data,

All the existing sensor are « user defined » this means that you can create a
sensor providing your RTT/jitter and packet loss.
However, this assumes that these indicators are available and visible from
RARE/freeRtr via a cli command.

> so I believe that using a protocol like SNMP integrating with a prometheus
> node exporter or zabbix,
> I could capture this kind of data, but I saw that there is no documentation
> for this.

It is planned to couple sensor logic with SNMP transport so that SNMP poller
can fetch sensor KPI <—> SNMP OID

However this does not change your problem. If the indicator is not visible
from the control plane then
wether you use SNMP or Prometheus, you won’t be able to retrieve it.

Now, depending on the cli output related the indicator, it might not be «
parsable ».

In that case, we might have to adjust the CLI output so that it can be
"prometheus friendly"

Look at the example here from grafana.com/dashboard:
https://grafana.com/grafana/dashboards/13153-rare-freerouter-interfaces-bytes/

The logic here is to launch _ANY_ possible CLI command and indicate freeRtr
to how to craft an indicator ready to be expert by prometheus agent.
For bytes you have then the command:
show interface hwsumm

Which gives the output:

AMS0001#show interface hwsumm
interface state tx rx drop
sdn1 up 18697381 38294274 0
sdn1.10 up 0 12411969 0
sdn1.20 up 0 12402503 0
sdn1.30 up 0 12405918 0
sdn2 up 35937637 82744766 0
sdn3 up 25208927 56863177 0
sdn3.101 up 0 446688 0
sdn3.102 up 0 9671957 0
sdn3.20 up 0 0 0
sdn3.2503 up 0 13768237 0
sdn3.30 up 0 0 0
sdn3.3068 up 0 8459343 0
sdn3.472 up 3994560 5100060 0

I’ll let you dissect the logic of the sensor definition and you’ll understand
how hardware counters are made available for Prometheus server.

Can you please indicate me which command you plan to use for packet
loss/jitter/rtt ?

All the best,
Frederic

> Le 10 avr. 2023 à 04:26, Gabriel Tetzner
> <> a écrit :
>
> Hi all,
>
> I am wanting to monitor some specific data regarding the network interfaces
> of freeRouter, mainly RTT, jitter and packet loss of the interfaces would
> be interesting data for me.
>
> How would I do this by integrating SNMP with freeRouter? I saw that for
> prometheus there is no specific sensor for this interface data, so I
> believe that using a protocol like SNMP integrating with a prometheus node
> exporter or zabbix, I could capture this kind of data, but I saw that there
> is no documentation for this.
>
> Context: I want to monitor this data to be able to implement a machine
> learning or artificial intelligence model, for this I wanted to start
> monitoring data that would be interesting to train a model.
>
> Therefore, I'm asking for tips that can help me in integrating SNMP with
> freeRouter.
>
> Att.




Archive powered by MHonArc 2.6.24.

Top of Page