Thanks. I just now (19 June) noticed your reply. I was able to use it to find
my probe’s “birthday to the second”.
> On Jun 6, 2024, at 21:16, Malte Tashiro wrote:
>
> Hey,
>
> On 6/7/24 00:52, Edward Lewis wrote:
>> I don’t know the first_connection_time, just the probe’s “birthday”. The
Hey,
On 6/7/24 00:52, Edward Lewis wrote:
I don’t know the first_connection_time, just the probe’s “birthday”. The
connected time’s resolution is to the minute, but the birthday is only the day,
not the minute.
While not shown on the webinterface, you can get the precise times via the API,
Not quite.
I don’t know the first_connection_time, just the probe’s “birthday”. The
connected time’s resolution is to the minute, but the birthday is only the day,
not the minute.
Is one ‘y’ = 365 days or 365.25 or 365.2422 days (commonly held numbers for
days in a year)?
> On Jun 6, 2024, a
Hello,
That calculation is simple: sum_of_connected_time / (now() -
first_connection_time)
Does this help answering your question?
Regards,
Robert
On Wed, Jun 5, 2024 at 9:28 PM Edward Lewis wrote:
>
> On my probe’s status page, there is an “All Time” “Time Connected” of 8y 343d
> 15h 30m. H
On my probe’s status page, there is an “All Time” “Time Connected” of 8y 343d
15h 30m. How many minutes are in a “y”?
Context: in trying to illustrate uptime (number of 9’s) I wanted to show how
long it would take to achieve different number of 9’s based on my probe’s
history. (It’s only at o
