Document and advertise data pipeline latency contract
Categories
(Data Platform and Tools :: Documentation and Knowledge Repo (RTMO), task, P3)
Tracking
(Not tracked)
People
(Reporter: klukas, Unassigned)
Details
Once we have a final configuration for the new batch sink (https://bugzilla.mozilla.org/show_bug.cgi?id=1625330) and have been operating stably on that for at least one month, we should document the contract for latency in the data pipeline, including expected latency in normal operation (~10 minutes), maximum latency before we're paged and start to intervene (~1 hour), and expected communication in cases where we miss this contract.
This should probably live in DTMO somewhere.
Once it's published, we should additionally advertise this documentation on fx-data-dev, #fx-metrics in Slack, and perhaps also the weekly data-announce email list. We should include in there a celebration of stability and cost savings.
Reporter | ||
Comment 1•3 years ago
|
||
This continues to be desirable. We should take this on in H2.
Reporter | ||
Updated•2 years ago
|
Description
•