Closed
Bug 1245125
Opened 8 years ago
Closed 3 years ago
Produce a breakdown of the ping sizes, per channel
Categories
(Data Platform and Tools :: Monitoring & Alerting, defect, P4)
Data Platform and Tools
Monitoring & Alerting
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Dexter, Unassigned)
References
(Blocks 1 open bug)
Details
This bug is about investigating the size of the main pings and producing a report to drive further work in this area. We should break the ping size by: - Top level fields (Environment, etc.) - Ping size bucket - Channels
Reporter | ||
Updated•8 years ago
|
Comment 1•8 years ago
|
||
(In reply to Alessio Placitelli [:Dexter] from comment #0) > - Top level fields (Environment, etc.) Note that we might need more detail for top-level fields like "environment", breaking them down further.
Updated•7 years ago
|
Component: Telemetry → Metrics: Pipeline
Priority: P3 → --
Product: Toolkit → Cloud Services
Whiteboard: [measurement:client]
Version: Trunk → unspecified
Updated•7 years ago
|
Priority: -- → P3
Updated•7 years ago
|
Points: --- → 3
Updated•7 years ago
|
status-firefox47:
affected → ---
Component: Metrics: Pipeline → Monitoring & Alerting
Product: Cloud Services → Data Platform and Tools
Updated•7 years ago
|
Priority: P3 → P4
Comment 2•3 years ago
|
||
we have in the past implemented some reporting on main ping sizes - so there is a working process to meet the needs when we see the main ping size increasing now.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•