This creates too many metrics in graphite, as each client gets its uniquely IDed metric name. We haven't used this metric since EventStreams has been online, so I think we can stop producing it.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Remove client specific rdkafka stats callback | mediawiki/services/eventstreams | master | +1 -11 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | fgiunchedi | T1075 Audit groups of metrics in Graphite that allocate a lot of disk space | |||
| Resolved | fgiunchedi | T160644 Eventstreams graphite disk usage | |||
| Resolved | Ottomata | T174435 Stop tracking EventStreams client lag in graphite |
Event Timeline
Comment Actions
Change 379236 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[mediawiki/services/eventstreams@master] Remove client specific rdkafka stats callback
Comment Actions
Change 379236 merged by Ottomata:
[mediawiki/services/eventstreams@master] Remove client specific rdkafka stats callback
Comment Actions
Hey @Zoranzoki21, thanks for the diligence, but we track our tasks on the Analytics-Kanban board, and use their open statuses to talk about them at a standup meeting every day. So, please don't close our tasks! :)
Thanks though!