We just had an incident where a config change caused EventStreams to not see any events for about 24 hours. We should monitor and alert on at least some of the message volume for topics we expose in EventStreams, perhaps revision-create and recentchange would be enough.
See: https://wikitech.wikimedia.org/w/index.php?title=Incident_documentation/20170829-EventStreams
Change 433161 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[operations/puppet@production] Alert if EventStreams recentchange endpoint has no messages
Change 433161 merged by Ottomata:
[operations/puppet@production] Alert if EventStreams recentchange endpoint has no messages
Change 433166 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[operations/puppet@production] Fix type in check_eventstreams script
Change 433166 merged by Ottomata:
[operations/puppet@production] Fix type in check_eventstreams script
Change 433194 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[operations/puppet@production] Use fqdn instead of localhost for curl eventstreams check
Change 433194 merged by Ottomata:
[operations/puppet@production] Use proper path and fqdn for eventstreams check