Consider localhost for haproxy stats

Bug #1950881 reported by Haw Loeung
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Telegraf Charm
New
Undecided
Unassigned

Bug Description

Hi,

When telegraf is related to haproxy (telegraf:haproxy <-> haproxy:statistics), it sets up /etc/telegraf/telegraf.d/haproxy.conf as follows:

| $ sudo cat /etc/telegraf/telegraf.d/haproxy.conf
|
| [[inputs.haproxy]]
| servers = ["http://haproxy:<REDACTED>@10.123.35.72:10000"]

We should consider retrieving haproxy stats from localhost / 127.0.0.1 instead.

Related branches

Eric Chen (eric-chen)
tags: added: good-first-bug
Eric Chen (eric-chen)
Changed in charm-telegraf:
status: New → Fix Committed
Haw Loeung (hloeung)
Changed in charm-telegraf:
status: Fix Committed → New
Revision history for this message
Eric Chen (eric-chen) wrote :

This issue was pending long time. Is it still valid?
Furthermore, soon or later, the monitoring system will migrate to COS. Telegraf will be replaced by grafana-agent. Therefore, we won't follow up this issue. But welcome to reopen it when anyone encounter this issue again.
(https://charmhub.io/topics/canonical-observability-stack)

Changed in charm-telegraf:
status: New → Won't Fix
Revision history for this message
Haw Loeung (hloeung) wrote :

Yeah, it's still valid, similar to the apache2 one - LP:1813288

Changed in charm-telegraf:
status: Won't Fix → New
Revision history for this message
Haw Loeung (hloeung) wrote :

It looks like this is fixed on the other side, HAproxy charm's end:

| https://code.launchpad.net/~cjwatson/charm-haproxy/listener-address-localhost/+merge/449723

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.