![](https://secure.gravatar.com/avatar/a8f7f23f357ea6a471f31f31a374575f.jpg?s=120&d=mm&r=g)
Hi,
I've checked around for some docs on this subject but I'm coming up empty. Not sure if I'm looking in the wrong spot or if they just don't exist.
I'm noticing the odd gap in all graphs for a particular device, and only that device. The two gaps in the last 24 hours seem to have lasted about 15 and 30 minutes, respectively. This is the first time I've seen these gaps on this device, but I did upgrade the code on this box last week. I'm convinced it's a software issue on the router I'm polling, but I need some ammo for the vendor. To that end, I'd like to enable some debugging that will show what the poller is reporting (or not reporting) when it hits this device. My hope is to catch something useful in the debugs that I can bring to the vendor. Any hits appreciated.
Thanks!
![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
There is no way to debug this without debugging everything with -d on the poller.
You could set up a separate instance of observium and drop /all/ polling debug output to a log file, but it would get large.
adam.
On Thu, 7 Mar 2013 15:53:57 -0500, Jason Lixfeld jason@lixfeld.ca wrote:
Hi,
I've checked around for some docs on this subject but I'm coming up
empty.
Not sure if I'm looking in the wrong spot or if they just don't exist.
I'm noticing the odd gap in all graphs for a particular device, and only that device. The two gaps in the last 24 hours seem to have lasted
about
15 and 30 minutes, respectively. This is the first time I've seen these gaps on this device, but I did upgrade the code on this box last week.
I'm
convinced it's a software issue on the router I'm polling, but I need
some
ammo for the vendor. To that end, I'd like to enable some debugging
that
will show what the poller is reporting (or not reporting) when it hits
this
device. My hope is to catch something useful in the debugs that I can bring to the vendor. Any hits appreciated.
Thanks!
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
![](https://secure.gravatar.com/avatar/a8f7f23f357ea6a471f31f31a374575f.jpg?s=120&d=mm&r=g)
So it's just -d, huh? I can do that and write it out to a file and hopefully parse through it.
Thanks for the tip.
On 2013-03-07, at 3:23 PM, Adam Armstrong adama@memetic.org wrote:
There is no way to debug this without debugging everything with -d on the poller.
You could set up a separate instance of observium and drop /all/ polling debug output to a log file, but it would get large.
adam.
On Thu, 7 Mar 2013 15:53:57 -0500, Jason Lixfeld jason@lixfeld.ca wrote:
Hi,
I've checked around for some docs on this subject but I'm coming up
empty.
Not sure if I'm looking in the wrong spot or if they just don't exist.
I'm noticing the odd gap in all graphs for a particular device, and only that device. The two gaps in the last 24 hours seem to have lasted
about
15 and 30 minutes, respectively. This is the first time I've seen these gaps on this device, but I did upgrade the code on this box last week.
I'm
convinced it's a software issue on the router I'm polling, but I need
some
ammo for the vendor. To that end, I'd like to enable some debugging
that
will show what the poller is reporting (or not reporting) when it hits
this
device. My hope is to catch something useful in the debugs that I can bring to the vendor. Any hits appreciated.
Thanks!
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (2)
-
Adam Armstrong
-
Jason Lixfeld