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
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
|
<!--
title: "PostgreSQL monitoring with Netdata"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/python.d.plugin/postgres/README.md
sidebar_label: "PostgreSQL"
-->
# PostgreSQL monitoring with Netdata
> **Warning**: This module is deprecated and will be deleted in v1.37.0.
> Use [go.d/postgres](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/postgres).
Collects database health and performance metrics.
## Requirements
- `python-psycopg2` package. You have to install it manually and make sure that it is available to the `netdata` user, either using `pip`, the package manager of your Linux distribution, or any other method you prefer.
- PostgreSQL v9.4+
Following charts are drawn:
1. **Database size** MB
- size
2. **Current Backend Processes** processes
- active
3. **Current Backend Process Usage** percentage
- used
- available
4. **Write-Ahead Logging Statistics** files/s
- total
- ready
- done
5. **Checkpoints** writes/s
- scheduled
- requested
6. **Current connections to db** count
- connections
7. **Tuples returned from db** tuples/s
- sequential
- bitmap
8. **Tuple reads from db** reads/s
- disk
- cache
9. **Transactions on db** transactions/s
- committed
- rolled back
10. **Tuples written to db** writes/s
- inserted
- updated
- deleted
- conflicts
11. **Locks on db** count per type
- locks
12. **Standby delta** KB
- sent delta
- write delta
- flush delta
- replay delta
13. **Standby lag** seconds
- write lag
- flush lag
- replay lag
14. **Average number of blocking transactions in db** processes
- blocking
## Configuration
Edit the `python.d/postgres.conf` configuration file using `edit-config` from the Netdata [config
directory](/docs/configure/nodes.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/postgres.conf
```
When no configuration file is found, the module tries to connect to TCP/IP socket: `localhost:5432` with the
following collection jobs.
```yaml
socket:
name : 'socket'
user : 'postgres'
database : 'postgres'
tcp:
name : 'tcp'
user : 'postgres'
database : 'postgres'
host : 'localhost'
port : 5432
```
**Note**: Every job collection must have a unique identifier. In cases that you monitor multiple DBs, every
job must have it's own name. Use a mnemonic of your preference (e.g us_east_db, us_east_tcp)
## Troubleshooting
To troubleshoot issues with the `postgres` collector, run the `python.d.plugin` with the debug option enabled. The output
should give you clues as to why the collector isn't working.
First, navigate to your plugins directory, usually at `/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
```
You can now run the `python.d.plugin` to debug the collector:
```bash
./python.d.plugin postgres debug trace
```
---
|
