Closed Bug 1474587 Opened 7 years ago Closed 4 years ago

Expose experiment status data from Telemetry

Categories

(Data Platform and Tools :: General, enhancement, P2)

enhancement
Points:
3

Tracking

(Not tracked)

RESOLVED INACTIVE

People

(Reporter: mreid, Unassigned)

Details

From Benson's comment on bug 1473691: More random ideas/questions: - Is there a way to make this pull based? For example, we could set up a polling service to check for data. This could work like a monitor too, alerting if no data for a study shows up in X hours - We could make this automated, PUSH based by publishing messages into SNS which distributes to SQS queues. This could downstream workflows like linking up telemetry with Delivery console ----- We have a few similar things in flight, such as bug 1465442 and bug 1470095. Sunah, how do you think we should approach this kind of thing?
Flags: needinfo?(ssuh)
For delivery console monitoring, I think the ideal would be to have the upcoming streaming events topic push out a statsd counter for each normandy event to, say, datadog, or wherever makes the most sense, dashboard-wise. Are there things we'd get from monitoring experiments in the main ping environment instead? I suppose the biggest thing is if we want to know current DAU for an experiment/rollout after enrollment phase (which is a common need).
Flags: needinfo?(ssuh)
Points: --- → 3
Priority: -- → P2

closing as experiment system has moved forward so much

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INACTIVE
Component: Datasets: Experiments → General
You need to log in before you can comment on or make changes to this bug.