If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Provide way to keep track of telemetry ping sizes

RESOLVED FIXED in Backlogged - BZ

Status

Mozilla Metrics
Data/Backend Reports
RESOLVED FIXED
6 years ago
3 years ago

People

(Reporter: (dormant account), Unassigned)

Tracking

unspecified
Backlogged - BZ
x86
Linux
Dependency tree / graph

Details

(Whiteboard: [Telemetry:P1])

(Reporter)

Description

6 years ago
We need to keep track of the ping size to make sure we aren't wasting the user bandwidth. This way we'll know if/when we need to switch to a more efficient protocol

Updated

5 years ago
Status: NEW → ASSIGNED

Updated

5 years ago
Whiteboard: Telemetry -- needs PM project priority

Comment 1

5 years ago
Triaged.
Assignee: deinspanjer → nobody
Target Milestone: Unreviewed → Backlogged - BZ
Blocks: 742496
Whiteboard: Telemetry -- needs PM project priority → [Telemetry:P1]
AFAIK Telemetry goes to S3, and isn't part of anything we have visibility into at this point in time. Is this report still desired?

Comment 3

3 years ago
We have this:
http://ec2-50-112-66-71.us-west-2.compute.amazonaws.com:4352/#sandboxes/TelemetryChannelMetricsAggregator/outputs/TelemetryChannelMetricsAggregator.ALL.cbuf
Great! Looks like total size is there, so I'll close this out.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.