Closed
Bug 1339655
Opened 8 years ago
Closed 8 years ago
Add SSL_HANDSHAKE_RESULT to main_summary
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ekr, Assigned: amiyaguchi)
References
Details
Attachments
(1 file)
I am trying to measure TLS failure behavior. Could you please add
SSL_HANDSHAKE_RESULT to the main_summary table.
|
||
Comment 1•8 years ago
|
||
please roll to a p1 when you start work
Assignee: nobody → amiyaguchi
Priority: -- → P2
|
|
Assignee | |
Updated•8 years ago
|
Priority: P2 → P1
|
|
Assignee | |
Comment 2•8 years ago
|
||
|
|
Assignee | |
Comment 3•8 years ago
|
||
This notebook[1] verifying the correctness of the new schema includes an example SQL query that does very simple exploration of the new fields.
The new schema comes with the addition of 3 new fields after some initial discussion[2].
1. ssl_handshake_result: Map[String, Integer] corresponding to error code and count
2. ssl_handshake_result_success: Count describing successful handshakes
3. ssl_handshake_result_failure: Count that includes error codes 1-671
[1] https://gist.github.com/acmiyaguchi/b7deaad26bac276a9fb7d3257d9c6151
[2] https://github.com/mozilla/telemetry-batch-view/pull/187#discussion_r104493681
|
|
Assignee | |
Comment 4•8 years ago
|
||
These fields should be available as of 20170307.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
|
||
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•