blob: 8ade512bb278e9aec31e298f5566835c6826c558 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
|
<!--
title: "HAProxy monitoring with Netdata"
custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/collectors/python.d.plugin/haproxy/README.md"
sidebar_label: "haproxy-python.d.plugin"
learn_status: "Published"
learn_topic_type: "References"
learn_rel_path: "Integrations/Monitor/Webapps"
-->
# HAProxy collector
Monitors frontend and backend metrics such as bytes in, bytes out, sessions current, sessions in queue current.
And health metrics such as backend servers status (server check should be used).
Plugin can obtain data from URL or Unix socket.
Requirement:
- Socket must be readable and writable by the `netdata` user.
- URL must have `stats uri <path>` present in the haproxy config, otherwise you will get HTTP 503 in the haproxy logs.
It produces:
1. **Frontend** family charts
- Kilobytes in/s
- Kilobytes out/s
- Sessions current
- Sessions in queue current
2. **Backend** family charts
- Kilobytes in/s
- Kilobytes out/s
- Sessions current
- Sessions in queue current
3. **Health** chart
- number of failed servers for every backend (in DOWN state)
## Configuration
Edit the `python.d/haproxy.conf` configuration file using `edit-config` from the Netdata [config
directory](/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`.
```bash
cd /etc/netdata # Replace this path with your Netdata config directory, if different
sudo ./edit-config python.d/haproxy.conf
```
Sample:
```yaml
via_url:
user: 'username' # ONLY IF stats auth is used
pass: 'password' # # ONLY IF stats auth is used
url: 'http://ip.address:port/url;csv;norefresh'
```
OR
```yaml
via_socket:
socket: 'path/to/haproxy/sock'
```
If no configuration is given, module will fail to run.
### Troubleshooting
To troubleshoot issues with the `haproxy` module, run the `python.d.plugin` with the debug option enabled. The
output will give you the output of the data collection job or error messages on why the collector isn't working.
First, navigate to your plugins directory, usually they are located under `/usr/libexec/netdata/plugins.d/`. If that's
not the case on your system, open `netdata.conf` and look for the setting `plugins directory`. Once you're in the
plugin's directory, switch to the `netdata` user.
```bash
cd /usr/libexec/netdata/plugins.d/
sudo su -s /bin/bash netdata
```
Now you can manually run the `haproxy` module in debug mode:
```bash
./python.d.plugin haproxy debug trace
```
|
