Closed
Bug 1184383
Opened 10 years ago
Closed 10 years ago
Add environment.settings.telemetryEnabled to UT elasticsearch index
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kparlante, Unassigned)
References
Details
(Whiteboard: [unifiedTelemetry])
It would be great to look at ping size data for the "base set" -- people in the pre-release population who have telemetryEnabled set to false.
We can do that in other ways (spark queries, heka filters), but if its easy, lets add that here.
|
||
Updated•10 years ago
|
Priority: -- → P2
Whiteboard: [40b7][unifiedTelemetry]
|
||
Comment 1•10 years ago
|
||
I added this in https://github.com/mozilla-services/data-pipeline/pull/100. Oddly, when I disable telemetry, the pings show up in kibana with telemetryEnabled missing (as opposed to false), but I haven't looked into it any further.
|
||
Updated•10 years ago
|
Iteration: --- → 43.1 - Aug 24
Whiteboard: [40b7][unifiedTelemetry] → [unifiedTelemetry]
|
|
||
Updated•10 years ago
|
Assignee: whd → nobody
|
|
||
Comment 2•10 years ago
|
||
Whd - can we close this? At this point Katie is able to get what she needs.
|
|
||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 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
•