This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] Minor nit in first monthly probe report after registration
- Previous message (by thread): [atlas] Minor nit in first monthly probe report after registration
- Next message (by thread): [atlas] Atlas probes in non-production networks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Johan ter Beest
jterbeest at ripe.net
Mon Jul 1 10:54:02 CEST 2024
Hi, You are absolutely correct and considering this is the monthly report, the data is also correct as the probe was not available for the beginning of the month. I understand that this sounds pedantic ;) As the connected time on the website does take all this information into account, I am not sure we want to change it for the monthly report. We could probably add the actual connected percentage as well. I will discuss this with the team. Cheers, Johan RIPE Atlas Team On Mon, 1 Jul 2024 at 10:28, ripe--- via ripe-atlas <ripe-atlas at ripe.net> wrote: > Resent, hopefully without HTML formatting this time (sorry for earlier) > > Hi, > > A minor nit with regards to the availability time in the monthly probe > report for the month the probe was registered in: > > The total availability indicated is bogus as the whole month is taken as > the calculation interval as its basis, rather than only the time since > probe registration. > > Calculation interval : 2024-06-01 00:00:00 - 2024-07-01 00:00:00 > Total Connected Time : 0d 14:40 > Total Disconnected Time : 29d 09:19 > Total Availability : 2.04% > > > +------------------+---------------------+---------------+-----------------------+ > | Disconnected for | Connected at (UTC) | Connected for | Disconnected at > (UTC) | > > +------------------+---------------------+---------------+-----------------------+ > | - | 2024-06-30 08:52:15 | 0d 00:36 | 2024-06-30 09:29:07 | > | 0d 00:04 | 2024-06-30 09:33:30 | 0d 03:20 | 2024-06-30 12:54:07 | > | 0d 00:01 | 2024-06-30 12:55:49 | 0d 00:04 | 2024-06-30 13:00:17 | > | 0d 00:04 | 2024-06-30 13:04:44 | 0d 01:35 | 2024-06-30 14:39:54 | > | 0d 00:01 | 2024-06-30 14:40:55 | 0d 00:32 | 2024-06-30 15:13:10 | > | 0d 00:10 | 2024-06-30 15:23:30 | 0d 00:02 | 2024-06-30 15:26:26 | > | 0d 00:05 | 2024-06-30 15:32:13 | 0d 08:27 | Still connected | > > +------------------+---------------------+---------------+-----------------------+ > > I guess just an optical issue rather than a problem, maybe a bit > misleading. The UI seems to take the fractional aspect into account, which > seems more relevant. > > Connection Information > > Probe's birthday: 2024-06-30 > > Time Connected Percent > Last Week 21h 11m 97.87% > Last Month 21h 11m 97.87% > All Time 21h 11m 97.87% > > Kind regards, > > R. > > -- > ripe-atlas mailing list > ripe-atlas at ripe.net > https://mailman.ripe.net/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20240701/9a68d85a/attachment.html>
- Previous message (by thread): [atlas] Minor nit in first monthly probe report after registration
- Next message (by thread): [atlas] Atlas probes in non-production networks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]