Page MenuHomePhabricator
Create Task
Maniphest T107515

Setup alerting for l10nupdate
Closed, DeclinedPublic
Actions

Description

Automated deploys should have a means to alert humans if something is wrong. l10nupdate currently does not other than a "failed" message in the SAL entry. This has been a problem in the past where l10nupdate was not completing successfully for more than a week yet no one noticed nor reported the issue. It wasn't until @greg noticed via his Twitter feed (where he subscribes to @wikimediatech) at the time of the failure.

An Icinga (or otherwise) alert based on the exit status of the l10nupdate run is needed.

Related Objects
Search...

Event Timeline

greg created this task.Jul 30 2015, 10:31 PM
greg raised the priority of this task from to Needs Triage.
greg updated the task description. (Show Details)
greg added a project: Deployments.
greg mentioned this in T107480: Remove (?) l10nupdate from !log'ing.
greg added subscribers: Legoktm, thcipriani, • demon and 4 others.
thcipriani triaged this task as Medium priority.Aug 5 2015, 4:07 PM
thcipriani moved this task from To Triage to Next: Maintenance on the Deployments board.
Nemo_bis added a subtask: T49301: [l10n] LocalisationUpdate can incorrectly report/log success.Sep 22 2015, 4:21 PM
Legoktm mentioned this in T158360: RFC: Reevaluate LocalisationUpdate extension for WMF.Mar 6 2017, 6:17 PM
• MZMcBride subscribed.Mar 7 2017, 1:06 AM

What does this task mean? Can someone please expand the task description or close this task?

greg renamed this task from Setup alerts for l10nupdate to Setup alerting for l10nupdate.Mar 7 2017, 6:24 PM
greg updated the task description. (Show Details)
greg added a project: observability.
• Nikerabbit subscribed.Mar 7 2017, 6:49 PM
• MZMcBride added a comment.Mar 11 2017, 2:00 PM

Thanks for the task description update.

We could, uhh, e-mail wikitech-l on failure? :-) Personally, it kind of feels like logging to the server admin log is (should be?) sufficient. If nobody notices a breakage for a week or longer, it seems the issue is perhaps self-prioritizing.

greg moved this task from Next: Maintenance to Backlog (Tech) on the Deployments board.Sep 26 2017, 10:59 PM
• Phabricator_maintenance moved this task from Backlog (Tech) to Localization on the Deployments board.Sep 26 2017, 11:20 PM
fgiunchedi moved this task from Inbox to Radar on the observability board.Jul 20 2020, 1:15 PM
• taavi closed this task as Declined.Jun 8 2023, 3:14 PM
• taavi closed subtask T49301: [l10n] LocalisationUpdate can incorrectly report/log success as Declined.
• taavi subscribed.

Per https://gerrit.wikimedia.org/r/c/operations/puppet/+/896318.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits