Jaime:
(Adding analytics e-mail list)
Please send notes regarding eventlogging to analytics@
Thanks,
Nuria
On Tue, Nov 3, 2015 at 9:03 AM, Jaime Crespo jcrespo@wikimedia.org wrote:
As actionables of https://wikitech.wikimedia.org/wiki/Incident_documentation/20151022-EventLog...
I have migrated the replication method used by Sean to puppet and added monitoring (which was missing initially). While the current state could be iteratively improved, it no longer depends from a single process on a single machine, that could be restarted or fail at any time. We also have logs and alerts to identify issues immediately. This will also allow purging rows easier and faster in the short future.
Of course, any migration could have regressions, so please monitor any issue you may find (as I am currently doing, and I have not yet found). This will hopefully prevent the issue to happen again.
Regards,
-- Jaime Crespo http://wikimedia.org
Awesome Jaime, thanks!
On Tue, Nov 3, 2015 at 6:25 PM, Nuria Ruiz nuria@wikimedia.org wrote:
Jaime:
(Adding analytics e-mail list)
Please send notes regarding eventlogging to analytics@
Thanks,
Nuria
On Tue, Nov 3, 2015 at 9:03 AM, Jaime Crespo jcrespo@wikimedia.org wrote:
As actionables of https://wikitech.wikimedia.org/wiki/Incident_documentation/20151022-EventLog...
I have migrated the replication method used by Sean to puppet and added monitoring (which was missing initially). While the current state could be iteratively improved, it no longer depends from a single process on a single machine, that could be restarted or fail at any time. We also have logs and alerts to identify issues immediately. This will also allow purging rows easier and faster in the short future.
Of course, any migration could have regressions, so please monitor any issue you may find (as I am currently doing, and I have not yet found). This will hopefully prevent the issue to happen again.
Regards,
-- Jaime Crespo http://wikimedia.org