Index: tools/metrics/histograms/histograms.xml |
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml |
index c1a6e079e4ea68d94640ec3541c4088f0b7d2507..1241bc95fbe8c3597d1c5e7c43add05e8ea7413a 100644 |
--- a/tools/metrics/histograms/histograms.xml |
+++ b/tools/metrics/histograms/histograms.xml |
@@ -18801,6 +18801,23 @@ Therefore, the affected-histogram name has to have at least one dot in it. |
</summary> |
</histogram> |
+<histogram name="Net.SSL_EVCertificateCTCompliance" |
+ enum="CTRequirementCompliance"> |
+ <owner>eranm@chromium.org</owner> |
+ <owner>rsleevi@chromium.org</owner> |
+ <summary> |
+ The state of compliance with Certificate Transparency presence requirements |
+ for each EV certificate. An EV certificate could be non-compliant (in which |
+ case it loses the EV status), comply through inclusion in the EV whitelist |
+ or have the required number of Signed Certificate Timestamps. This metric |
+ will gauge adoption rate of Certificate Transparency and will help identify |
+ when the EV whitelist is no longer needed. Emitted during every SSL |
+ connection establishment, but only if the client is checking compliance with |
+ Certificate Transparency requirements (currently guarded by a Finch |
+ experiment). |
+ </summary> |
+</histogram> |
+ |
<histogram name="Net.SSL_EVCertificateInWhitelist" enum="Boolean"> |
<owner>eranm@chromium.org</owner> |
<owner>rsleevi@chromium.org</owner> |
@@ -42809,6 +42826,12 @@ Therefore, the affected-histogram name has to have at least one dot in it. |
<int value="8" label="PlayMusic"/> |
</enum> |
+<enum name="CTRequirementCompliance" type="int"> |
+ <int value="0" label="Not Compliant"/> |
+ <int value="1" label="Whitelisted"/> |
+ <int value="2" label="Has enough SCTs"/> |
+</enum> |
+ |
<enum name="DailyEventIntervalType" type="int"> |
<int value="0" label="First Run"/> |
<int value="1" label="Day Elapsed"/> |