Suppose I look at at probe with a URL like this
https://atlas.ripe.net/probes/xxxxxxx/overview
Looking at the Event Log, the “Connected For” column only shows the hours:minutes:seconds even if the actual time is for multiple days.
See example on screenshot - the uptime is some seven days plus eight hours or so - but you only see the “remainder”.
Is this as intended, or is there a way of getting the “days” included too.
Hi Daksol,
Thanks for reporting this. The best place to see “connected for” timings is in the network panel (at the bottom) under “Connection History”:
https://atlas.ripe.net/probes/xxxxxxx/network
The Event log, on the other hand, is meant to combine several different types of events from several different sources to simply show the timestamps of those reports in one place for debugging purposes. We will be removing the “connected for” and “disconnected for” columns from this table in the near future to avoid this confusion.
Kind regards,
Stephen
Atlas UI
The issue is incorrect reporting of time - one of many, in fact. Removing the column rather than fixing the actual bug does not reflect well on the Atlas team. (I do applaud adding “events” to the normal UI. It’s always existed, but you had to know where to go to see it.) If you’re going to make previously “internal” diagnostic information public, you’re going to need to support public use of it.
