|operations/puppet : production||Disable eventlogging-consumer mysql in prod|
|operations/puppet : production||Remove unused eventlogging mysql consumer eventbus puppetization|
|operations/puppet : production||Use $ensure for all resources in eventlogging::service::consumer|
|operations/puppet : production||Disable mysql-eventbus eventlogging consumer|
|Open||Ottomata||T159170 Sunset MySQL data store for eventlogging|
|Resolved||Ottomata||T232349 Disable production EventLogging analytics MySQL consumers|
- Mentioned In
- T231858: Archive data on eventlogging MySQL to analytics replica before decomisioning
- Mentioned Here
- T223414: Move reportupdater reports that pull data from eventlogging mysql to pull data from hadoop
T229862: Port reportupdater queries that use MySQL log eventlogging database to Hive event database
Since the page-create MySQL based dashboards are no longer needed, can we go ahead and just turn off the mysql-eventbus EventLogging consumer? Does anyone else use any MediaWiki/EventBus tables on the eventlogging log database?
This look related,
CRITICAL - degraded: The system is operational but one or more units failed.
eventlog1002:~$ sudo systemctl [...] ● email@example.com not-found failed failed eventl
I ACK'ed the alert, with a pointer to that task.
Something strange happened today: I noticed in icinga that the eventlogging mysql insertion rate alarm was in UNKNOWN state, so I checked the graphs and the m4 consumer stopped sending data around the 21st:
I bounced the consumer on eventlog1002, and now events are re-flowing.. Didn't see anything in here or in the SAL mentioning that m4 was also stopped on purpose, let me know if I need to re-stop it or not.. Super strange that the alarm didn't fire!