[atlas]too many disconnects?
- Previous message (by thread): [atlas]too many disconnects?
- Next message (by thread): [atlas]too many disconnects?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Fri Mar 4 15:29:22 CET 2011
Hi, On 2011.03.04. 14:26, Wilfried Woeber, UniVie/ACOnet wrote: > [my apologies to the Team for the duplicate, I 1st picked the wrong address] > > > Q to the Team and to the Probe Hosts: > > > My feeling is that the probes do register too many "disconnects". > I just had a look at the two under my control and the numbers of transitions > are - > > 466: 25 events between 2010-12-21 07:14:30 UTC and 2011-03-01 10:24:11 UTC > 414: 25 events between 2010-11-22 12:31:02 UTC and 2011-02-20 20:18:24 UTC > > While there may be a local reason for some of the down-periods, I doubt > that I had so many outages on my ends. Is anyone else seeing a similar > pattern? Disconnects and reconnects are expected; the probes are somewhat sensitive in this regard. Most of these downtimes should be less than 5, at most 10 minutes. This is normal, don't worry about them. > Regarding presentation, again, could we please have an additional item of > "Total Downtime" (next to the "Total Uptime"), and the duration of the downs > in the 25 lines with the time stamps? This would make it much more straight- > forward to spot patterns.... Yes, this is in fact already working in our test environment! ETA for public rollout is next week. > Minor cosmetics, relevant when reporting stuff, could the probe's number > be displayed somewhere in the Probe Conf panel (e.g. in the line with the > Firmware Version)? Sure. Cheers, Robert > Thanks for your consideration, > have a nice weekend > Wilfried
- Previous message (by thread): [atlas]too many disconnects?
- Next message (by thread): [atlas]too many disconnects?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]