Additional log compliance monitoring data available

[Joe DeBlasio]

Hi folks,

Chrome publishes data on what our log monitoring infrastructure sees for CT logs recognized by Chrome. This data is used internally in evaluating logs against our availability requirements, and is provided externally to make it easier for log operators to proactively detect and mitigate log availability issues.

Though tools exist to make it easier, we've received feedback that the 90-day averages in those CSVs can be difficult to interpret, particularly when trying to understand recent log performance.

We are now also publishing https://www.gstatic.com/ct/compliance/endpoint_uptime_24h.csv, which retains the same format as endpoint_uptime.csv but lists averages only over requests made in the 24 hours preceding publication. This file is published daily at the same time that endpoint_uptime.csv is updated. That means that all data in this file is also reflected in endpoint_uptime.csv, but we hope this new view may be easier to use for some consumers.

Questions always welcome,

Joe, on behalf of the Chrome CT Team

[Matthew McPherrin]

Hi Joe,

Approximately what time is the file updated?

Is the `last-modified` HTTP header's timestamp reliable for determining that in this system?

I appreciate the effort to make your data easier to process!

Matthew

--
You received this message because you are subscribed to the Google Groups "Certificate Transparency Policy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ct-policy+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/ct-policy/CAFZs0S7y2VOxLUtBt4_ZjOKT3Psb4GhZj5Nc4Zj%2BYzJ3b6zG5A%40mail.gmail.com.

[Joe DeBlasio]

Yes, the last-modified header is reliable for determining freshness.

Perhaps even bigger news is that that file is updated roughly every 45 minutes, not daily as I previously stated. Even better. 

Joe