- kafka consumer group lag
- purged-local backlog number
- purged_event_lag metric
Description
Description
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Restricted Task | |||||
| Duplicate | None | T109331 Deleted files sometimes remain visible to non-privileged users if permanently linked | |||
| Duplicate | None | T133819 upload-lb.ulsfo.wikimedia.org still allow access to some deleted files | |||
| Duplicate | BBlack | T119038 Image cache issue when 'over-writing' an image on commons | |||
| Resolved | • ema | T133821 Make CDN purges reliable | |||
| Resolved | • ema | T256444 several purgeds badly backlogged (> 10 days) | |||
| Resolved | CDanis | T256446 monitoring & alerting for purged |
Event Timeline
Comment Actions
Change 608019 had a related patch set uploaded (by Ema; owner: Ema):
[operations/puppet@production] purged: alert in case of high event lag
Comment Actions
Change 608019 merged by Ema:
[operations/puppet@production] purged: alert in case of high event lag
Comment Actions
Change 608564 had a related patch set uploaded (by Ema; owner: Ema):
[operations/puppet@production] purged: alert if local backlog grows past the given limits
Comment Actions
Change 608564 merged by Ema:
[operations/puppet@production] purged: alert if local backlog grows past the given limits
Comment Actions
@CDanis all done except for rdkafka_consumer_topics_partitions_consumer_lag, there's silence on grafana.wikimedia.org/explore when looking for that metric, even going back one month. Let me know if you think, for the scope of this ticket, that event-lag and local-backlog are enough.