Issue with traffic volume graph for asymmetric interfaces.
![](https://secure.gravatar.com/avatar/5f2e414f51e4c5b222a8fc3da321398a.jpg?s=120&d=mm&r=g)
Hi guys,
I have problem with graphing traffic graphs for one of my Observium monitored device; problem occurs when it comes to graph traffic for asymmetric interfaces - ones that only send or receive traffic. The problem is that when such interface is queried on the device for actual traffic values the response is:
for only-sending interface: Rx OID -> noSuchInstance, TxOID -> actual bits for only-receiving interface: Rx OID -> actual bits, TxOID -> noSuchInstance
Those values as used then to populate corresponding RRD file which results in series of "NaN"s for INOCTETS or OUTOCTETS data stores. The result is that traffic graph plotted from this RRD is corrupted - like this example: http://i66.tinypic.com/7281fo.png
Currently my Observium instance is at revision 7167. Could you share with me any ideas how to resole this issue?
Thank you & Regards! Pawel
![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
Hi,
This is an issue with the way rrdtool draws its scale.
We don't set min/max scales on bits graphs, since they're expected to have things above and below the zero line.
I'm not sure of the solution, does anyone else have an idea?
adam. On 04/11/2015 22:20:11, T-MONT Administrator admin@t-mont.net.pl wrote: Hi guys,
I have problem with graphing traffic graphs for one of my Observium monitored device; problem occurs when it comes to graph traffic for asymmetric interfaces - ones that only send or receive traffic. The problem is that when such interface is queried on the device for actual traffic values the response is:
for only-sending interface: Rx OID -> noSuchInstance, TxOID -> actual bits for only-receiving interface: Rx OID -> actual bits, TxOID -> noSuchInstance
Those values as used then to populate corresponding RRD file which results in series of "NaN"s for INOCTETS or OUTOCTETS data stores. The result is that traffic graph plotted from this RRD is corrupted - like this example: http://i66.tinypic.com/7281fo.png
Currently my Observium instance is at revision 7167. Could you share with me any ideas how to resole this issue?
Thank you & Regards! Pawel _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
![](https://secure.gravatar.com/avatar/5f2e414f51e4c5b222a8fc3da321398a.jpg?s=120&d=mm&r=g)
Hi,
I'm not sure if this is the right approach to fix this but maybe implementing of some kind of switch which will tell pooling engine that this particular interface is asymmetric one (Rx or Tx)?
When activated it could: 1. Prevent Observium from querying not-existing OIDs and force pooling engine to put 0 (zero) in INOCTETS or OUTOCTETS DS, OR 2. Force Observium to create RRD without non-existing data store (INOCTETS or OUTOCTETS).
Regards, Pawel
![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
The graph layout has nothing at all to do with anything the poller does.
It's a function of rrdtool's graph drawing.
adam. On 05/11/2015 07:22:19, T-MONT Administrator admin@t-mont.net.pl wrote: Hi,
I'm not sure if this is the right approach to fix this but maybe implementing of some kind of switch which will tell pooling engine that this particular interface is asymmetric one (Rx or Tx)?
When activated it could: 1. Prevent Observium from querying not-existing OIDs and force pooling engine to put 0 (zero) in INOCTETS or OUTOCTETS DS, OR 2. Force Observium to create RRD without non-existing data store (INOCTETS or OUTOCTETS).
Regards, Pawel _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
![](https://secure.gravatar.com/avatar/5f2e414f51e4c5b222a8fc3da321398a.jpg?s=120&d=mm&r=g)
I know that but that's the pooling engine job to deliver proper data which then will be used by rrdtool when plotting image. Honestly speaking I'm not sure of the other approach to solve this issue :(
Regards, Pawel
The graph layout has nothing at all to do with anything the poller does.
It's a function of rrdtool's graph drawing.
adam.
![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
I think part of the issue is caused by us 'blanking' the data when in or out counters are NaN.
Fixing this would need a little bit of rewriting of the graph definition.
adam. On 05/11/2015 07:55:53, T-MONT Administrator admin@t-mont.net.pl wrote: I know that but that's the pooling engine job to deliver proper data which then will be used by rrdtool when plotting image. Honestly speaking I'm not sure of the other approach to solve this issue :(
Regards, Pawel
The graph layout has nothing at all to do with anything the poller does.
It's a function of rrdtool's graph drawing.
adam.
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (2)
-
Adam Armstrong
-
T-MONT Administrator