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]
Description
Description
Event Timeline
Comment Actions
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]
Comment Actions
Change 283210 had a related patch set uploaded (by BBlack):
HTTPS for graphite monitor URLs T132461
Comment Actions
Change 283214 had a related patch set uploaded (by BBlack):
graphite.wm.o HTTPS redirect T132461
Comment Actions
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...