I have Dude v.2.0 and it is great so far except for the follwoing:
For some of the links when I hover with the mouse to see the bit rate, I find pupup graph appears (which means it is graph bit rate for this link is enabled),but there is no graph.
The interface name is shown with its other parameters, only the graph doesn’t show.
I have to open the settings dialogue for that link and disable bit rate graphing and then re enable it to have the graphing starting from that point agin.
I have done this many times for many links, but it keeps on doing it.
I hope you find a solution for this problem.
Restore a backup.
I’ve had the same issue, it means something is broken in your config AFAIK.
The Dude is great! But not always a stable as you’d like. I make an effort to backup The Dude (export button) two, three times a week (it’s done in a minute).
Hi there,
I’ve a similar problem with the values The Dude graphs for me..
When I change/adjust the probe (or function) it’s normal that The Dude starts again from 0, because of this I get a lot of gaps within the graphs.
Besides this occurence The Dude will just a little to frequently fail to graph a value whether you changed something or not. These gaps show themselves mainly when having a look at Hourly graphs, when you change time scale to day/month you can’t find the gaps anymore (even those of over hours a day..).
Anyone able to shed some light on the ‘why’ The Dude does this?
BTW: would really like a weekly graph within the Dude..
Regards,
Minollie
Gaps in graphs could simply mean the device has (temporarily) not returned answers to The Dude’s SNMP queries…
Not to say The Dude does not behave quirky sometimes…
Hi Winkelman,
The problem isn’t that the device hasn’t returned data to The Dude, which would indicate that the device is experiencing troubles one way or another, the value gets displayed within the label. Other monitoring-software that probe the devices never show a gap within the graphs, even while other things are checking the same device simultaniously.
The weird thing is that these gaps appear on irregular times without any obvious reason while the device remains reachable.
Regards,
Minollie
I am still facing the same problem up to and including v2.2 and 3B3