Page MenuHomePhabricator

prometheus-trafficserver-exporter: InsecureRequestWarning
Closed, DeclinedPublic

Description

The following warning occurs frequently on all cache hosts:

May 18 08:18:51 cp3054 prometheus-trafficserver-exporter[19895]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
May 18 08:18:51 cp3054 prometheus-trafficserver-exporter[19895]:   InsecureRequestWarning)

There are two problems to fix here: (1) the warning itself, obviously, and (2) it isn't clear which of the two prometheus-trafficserver-exporter services is issuing the warning (prometheus-trafficserver-tls-exporter.service or prometheus-trafficserver-backend-exporter.service). I think that setting SyslogIdentifier=%N in the unit should address (2), but I haven't tried.

Event Timeline

in this case is pretty obvious, ats-tls is the only instance listening on port 443 (TLS), but yeah, +1 to provide unique SylogIdentifiers

BBlack subscribed.

The swap of Traffic for Traffic-Icebox in this ticket's set of tags was based on a bulk action for all such tickets that haven't been updated in 6 months or more. This does not imply any human judgement about the validity or importance of the task, and is simply the first step in a larger task cleanup effort. Further manual triage and/or requests for updates will happen this month for all such tickets. For more detail, have a look at the extended explanation on the main page of Traffic-Icebox . Thank you!

BCornwall subscribed.

This warning is no long longer applicable since we've moved away from ats-tls. For good measure I verified that the error message does not manifest in any of the cp instances any more.

If there's still a desire to set unique syslog identifiers please do reopen this ticket. Thanks!