I don't have the details yet, but according to rumor, eventlogging data is not being recorded to the database.
|Open||None||T45250 Redo /beacon/impression system (formerly Special:RecordImpression) to remove extra round trips on all FR impressions (title was: S:RI should pyroperish)|
|Declined||None||T90917 Get banner count via Special:BannerLoader|
|Duplicate||None||T105109 Create UI for limiting banner impressions (banner diet?)|
|Resolved||• atgo||T78089 [epic] Banner History MVP|
|Resolved||None||T112020 [Mini epic] Activate Banner History!|
|Resolved||None||T112926 Beta Cluster EventLogging data is disappearing?|
eventlogging and database have been moved to deployment-eventlogging03 instance. Needed to upgrade from Precise to Trusty. Please use that instance now, deployment-eventlogging02 will be removed.
I apologize for the lack of an announcement on this. What is the proper channel?
- Absolute minimum: use !log in #wikimedia-releng so it shows up here: https://tools.wmflabs.org/sal/releng (or if you're old school: https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL). Think just like you would with production.
- Emailing appropriate lists if it can have a big impact (eg qa@lists and any other relevant one).
Ok, thanks. I think I migrated this service very hastily, since we were changing puppetization for production, which broke in labs because the changes didn't work on Precise.
Next time will do that. Can I email qa@lists or do I need to join?
"deployment-eventlogging02:/var full due to massive eventlogging_processor-server-side-0.log.1 ("(MainThread) Unable to process" errors)"