Description
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Switch safe browsing checks to HTTPS | operations/puppet | production | +9 -9 | |
| Update safe browsing checks | operations/puppet | production | +9 -9 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T31068 MediaWiki bugs to be fixed for 1.18wmf1 deployment (tracking) | |||
| Resolved | None | T30898 Set up notification for when/if Google's safe browsing spots something on wiki* | |||
| Resolved | Dzahn | T216985 google safe browsing icinga checks sporadic UNKNOWN due to 404 | |||
| Resolved | akosiaris | T116099 Google Safe Browsing Monitoring turned CRIT (rewrite check using the real API) |
Event Timeline
16:00 < icinga-wm> CUSTOM - Host google is UP: PING OK - Packet loss = 0%, RTA = 9.61 ms
16:02 < Krenair> mutante, I think they decided to move the page or something
Change 247754 had a related patch set uploaded (by MaxSem):
Update safe browsing checks
Change 247760 had a related patch set uploaded (by MaxSem):
Switch safe browsing checks to HTTPS
should this use the real API ?
"The API key format has changed. API keys are now managed in the Google Developers Console,"
who has that console and a key ?:)
i'll still say priority normal since this is broken monitoring (due to Google changing things on their side), not actual alarms that our sites have a problem
or anyone, can you fix https://gerrit.wikimedia.org/r/#/c/247760/2/modules/icinga/manifests/gsbmonitoring.pp with different options of check_http? i tried with -f follow , -f sticky among other things but did not find a solution