Dear Hosts, We've now enabled two features that were requested by hosts earlier: 1. The "Probe DNS" function allows you to ask for a DNS entry for you probe. Operational details: * The exact DNS name of your probe depends on your settings (simple or obfuscated), and can be looked up on the "Probe Conf" section of the probe status page. * The zone file is re-generated every 15 minutes. * The resulting address is the one we observe when the probe to connects to our infrastructure, so if you're using NAT then it's the public address of the NAT device. Currently it's either IPv4 or IPv6, but not both. We'll add the "other address" too in the future. 2. The probe uptime section has more details. It now contains: * Relative uptime for the last week and month, and for the full lifetime. * The source IP address of the individual connections. * The amount of up- and downtime (in days/hours/minutes), for each connection. Regards, Andreas
Hi Andreas, Team! Andreas Strikos wrote:
Dear Hosts, [...] 2. The probe uptime section has more details. It now contains: * Relative uptime for the last week and month, and for the full lifetime. * The source IP address of the individual connections. * The amount of up- and downtime (in days/hours/minutes), for each connection.
Great stuff! Is there a "cheap" way to upgrade the blue bar ("UPTIME") to plot data availability against uptime of the control connection?
Regards, Andreas
For the time being until resolved, I am looking for some machanism to detect at first glance that the delivery of measurement data is not functioning. I also noticed a change in panel labelling: Built-in Measurements :-) Thanks, Wilfried.
participants (2)
-
Andreas Strikos
-
Wilfried Woeber, UniVie/ACOnet