Haproxy go.d configuration for stats page

Help
, ,
1

Problem/Question

We are moving from python.d collectors and have problem with go.d version. Our configuration is:
haproxy.cfg:

listen stats 
 bind :::1936
 stats enable
 stats uri /

python.d/haproxy.conf

socket: '/var/run/haproxy/admin.sock'

Now how to configure haproxy go.d collector?
go.d/haproxy.conf:

jobs:
 - name: local
   url: http://[::1]:1936/;csv

[ DEBUG ] build[manager] build.go:154 received config group ('/etc/netdata/go.d/haproxy.conf'): 1 jobs (added: 1, removed: 0)
[ DEBUG ] build[manager] build.go:303 building haproxy[local] job, config: map[__provider__:file reader __source__:/etc/netdata/go.d/haproxy.conf autodetection_retry:0 module:haproxy name:local priority:70000 update_every:1 url:http://127.0.0.1:1936/;csv]
[ ERROR ] haproxy[local] haproxy.go:80 unsupported character in float
[ ERROR ] haproxy[local] job.go:191 check failed

go.d/haproxy.conf:

jobs:
 - name: local
   url: http://127.0.0.1:1936/

[ DEBUG ] build[manager] build.go:154 received config group ('/etc/netdata/go.d/haproxy.conf'): 1 jobs (added: 1, removed: 0)
[ DEBUG ] build[manager] build.go:303 building haproxy[local] job, config: map[__provider__:file reader __source__:/etc/netdata/go.d/haproxy.conf autodetection_retry:0 module:haproxy name:local priority:70000 update_every:1 url:http://127.0.0.1:1936/]
[ ERROR ] haproxy[local] haproxy.go:80 "INVALID" is not a valid start token
[ ERROR ] haproxy[local] job.go:191 check failed

Even using ’ or " doesn’t work.

Relevant docs you followed/actions you took to solve the issue

Environment/Browser/Agent’s version etc

agent 1.38.1

What I expected to happen

Data from stats page. Curl under netdata user returns stats data.

2

From the documentation it looks like the PROMEX module is required. That module exposes the metrics in the Prometheus format, accessible by default at http://xxx:8404/metrics, based on what I see in the config file.

I’m personally not sure what’s on port 1936 or what the ;csv is supposed to mean, perhaps this is a legacy way of exporting metrics that the old collector used.

3

Thank you, i missed this part. Anyway, i must revert to python.d module because netdata go.d module supports backends stats only.

4

We need to extend it to support the other metrics too then. @ilyam8 ?