Page MenuHomePhabricator

HTTPS redirects for graphite.wikimedia.org
Closed, ResolvedPublic

Description

Enabling this is trivial, the question is: is there any reason we *can't* enable this? Who's responsible for this service and might know of exceptions like mixed-content, or HTTPS-incapable tools which rely on it, etc? [note this a generic message being tacked into the description of several similar tickets]

Related Objects

StatusAssignedTask
Resolvedema
OpenBBlack
OpenBBlack
ResolvedBBlack
ResolvedArielGlenn
ResolvedChmarkine
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedCCogdill_WMF
DeclinedBBlack
DuplicateBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack
ResolvedBBlack

Event Timeline

BBlack created this task.Apr 12 2016, 3:43 PM
BBlack added a subscriber: fgiunchedi.

the most critical I can think of is check_graphite which already supports https (not sure about following redirects)

$ /usr/lib/nagios/plugins/check_graphite -U https://graphite.wikimedia.org check_threshold servers.neon.cpu.total.idle -C 10 -W 10 --under
OK: Less than 1.00% under the threshold [10.0]

Change 283210 had a related patch set uploaded (by BBlack):
HTTPS for graphite monitor URLs T132461

https://gerrit.wikimedia.org/r/283210

Change 283210 merged by BBlack:
HTTPS for graphite monitor URLs T132461

https://gerrit.wikimedia.org/r/283210

Change 283214 had a related patch set uploaded (by BBlack):
graphite.wm.o HTTPS redirect T132461

https://gerrit.wikimedia.org/r/283214

With the check_graphite stuff switched to HTTPS, so far neon doesn't seem to be suffering from any significant increase in overall CPU utilization. I think we're ok here...

Change 283214 merged by BBlack:
graphite.wm.o HTTPS redirect T132461

https://gerrit.wikimedia.org/r/283214

BBlack closed this task as Resolved.Apr 13 2016, 4:44 PM
BBlack claimed this task.