Provide some queries to monitor glean go-live in FFTV
Categories
(Data Platform and Tools :: Glean: SDK, task, P1)
Tracking
(Not tracked)
People
(Reporter: chutten, Assigned: chutten)
References
Details
Glean will, if it merges without further issue, be going live in FFTV soon (May 27). We should write some queries to monitor the launch to make sure nothing has gone obviously awry in its Telemetry.
The FFTV team will be monitoring Sentry for crash reports over the launch, and have their own dashboard for product health, so we should focus on things not already covered by this.
I'm thinking hourly-resolution plots that show the last couple of launches as context for client and ping counts according to the "core" ping. A seq
hole analysis might be taking it a bit far (if there are holes we'd expect strangeness in both the ping and client counts)... but it might be nice to have.
Assignee | ||
Comment 1•5 years ago
|
||
To start I have prepared
- "core" ping counts per hour per version - Allows us to examine "core" ping volumes over time and compare to past launches.
- client counts per hour per version - Allows us to examine how the client counts change compared to past launches. Need both this and the ping volumes to get a grasp on the health of the Telemetry system.
ni?gfritzsche to suggest other timely metrics that could be helpful and to maybe connect the dots so I can have a conversation with FFTV folks about what they might want/need as part of this project.
Assignee | ||
Comment 2•5 years ago
|
||
Georg helped connect me with ashleyt and :liuche and they're satisfied.
Updated•5 years ago
|
Description
•