]> git.proxmox.com Git - ceph.git/blame - ceph/doc/mgr/influx.rst
update sources to 12.2.7
[ceph.git] / ceph / doc / mgr / influx.rst
CommitLineData
3efd9988
FG
1=============
2Influx Plugin
3=============
4
5The influx plugin continuously collects and sends time series data to an
6influxdb database.
7
8The influx plugin was introduced in the 13.x *Mimic* release.
9
10--------
11Enabling
12--------
13
14To enable the module, use the following command:
15
16::
17
18 ceph mgr module enable influx
19
20If you wish to subsequently disable the module, you can use the equivalent
21*disable* command:
22
23::
24
25 ceph mgr module disable influx
26
27-------------
28Configuration
29-------------
30
31For the influx module to send statistics to an InfluxDB server, it
32is necessary to configure the servers address and some authentication
33credentials.
34
35Set configuration values using the following command:
36
37::
38
39 ceph config-key set mgr/influx/<key> <value>
40
41
42The most important settings are ``hostname``, ``username`` and ``password``.
43For example, a typical configuration might look like this:
44
45::
46
47 ceph config-key set mgr/influx/hostname influx.mydomain.com
48 ceph config-key set mgr/influx/username admin123
49 ceph config-key set mgr/influx/password p4ssw0rd
50
51Additional optional configuration settings are:
52
53:interval: Time between reports to InfluxDB. Default 5 seconds.
54:database: InfluxDB database name. Default "ceph". You will need to create this database and grant write privileges to the configured username or the username must have admin privileges to create it.
55:port: InfluxDB server port. Default 8086
28e407b8
AA
56:ssl: Use https connection for InfluxDB server. Use "true" or "false". Default false
57:verify_ssl: Verify https cert for InfluxDB server. Use "true" or "false". Default true
3efd9988
FG
58
59---------
60Debugging
61---------
62
63By default, a few debugging statments as well as error statements have been set to print in the log files. Users can add more if necessary.
64To make use of the debugging option in the module:
65
66- Add this to the ceph.conf file.::
67
68 [mgr]
69 debug_mgr = 20
70
71- Use this command ``ceph tell mgr.<mymonitor> influx self-test``.
72- Check the log files. Users may find it easier to filter the log files using *mgr[influx]*.
73
74--------------------
75Interesting counters
76--------------------
77
78The following tables describe a subset of the values output by
79this module.
80
81^^^^^
82Pools
83^^^^^
84
85+---------------+-----------------------------------------------------+
86|Counter | Description |
87+===============+=====================================================+
88|bytes_used | Bytes used in the pool not including copies |
89+---------------+-----------------------------------------------------+
90|max_avail | Max available number of bytes in the pool |
91+---------------+-----------------------------------------------------+
92|objects | Number of objects in the pool |
93+---------------+-----------------------------------------------------+
94|wr_bytes | Number of bytes written in the pool |
95+---------------+-----------------------------------------------------+
96|dirty | Number of bytes dirty in the pool |
97+---------------+-----------------------------------------------------+
98|rd_bytes | Number of bytes read in the pool |
99+---------------+-----------------------------------------------------+
100|raw_bytes_used | Bytes used in pool including copies made |
101+---------------+-----------------------------------------------------+
102
103^^^^
104OSDs
105^^^^
106
107+------------+------------------------------------+
108|Counter | Description |
109+============+====================================+
110|op_w | Client write operations |
111+------------+------------------------------------+
112|op_in_bytes | Client operations total write size |
113+------------+------------------------------------+
114|op_r | Client read operations |
115+------------+------------------------------------+
116|op_out_bytes| Client operations total read size |
117+------------+------------------------------------+
118
119
120+------------------------+--------------------------------------------------------------------------+
121|Counter | Description |
122+========================+==========================================================================+
123|op_wip | Replication operations currently being processed (primary) |
124+------------------------+--------------------------------------------------------------------------+
125|op_latency | Latency of client operations (including queue time) |
126+------------------------+--------------------------------------------------------------------------+
127|op_process_latency | Latency of client operations (excluding queue time) |
128+------------------------+--------------------------------------------------------------------------+
129|op_prepare_latency | Latency of client operations (excluding queue time and wait for finished)|
130+------------------------+--------------------------------------------------------------------------+
131|op_r_latency | Latency of read operation (including queue time) |
132+------------------------+--------------------------------------------------------------------------+
133|op_r_process_latency | Latency of read operation (excluding queue time) |
134+------------------------+--------------------------------------------------------------------------+
135|op_w_in_bytes | Client data written |
136+------------------------+--------------------------------------------------------------------------+
137|op_w_latency | Latency of write operation (including queue time) |
138+------------------------+--------------------------------------------------------------------------+
139|op_w_process_latency | Latency of write operation (excluding queue time) |
140+------------------------+--------------------------------------------------------------------------+
141|op_w_prepare_latency | Latency of write operations (excluding queue time and wait for finished) |
142+------------------------+--------------------------------------------------------------------------+
143|op_rw | Client read-modify-write operations |
144+------------------------+--------------------------------------------------------------------------+
145|op_rw_in_bytes | Client read-modify-write operations write in |
146+------------------------+--------------------------------------------------------------------------+
147|op_rw_out_bytes | Client read-modify-write operations read out |
148+------------------------+--------------------------------------------------------------------------+
149|op_rw_latency | Latency of read-modify-write operation (including queue time) |
150+------------------------+--------------------------------------------------------------------------+
151|op_rw_process_latency | Latency of read-modify-write operation (excluding queue time) |
152+------------------------+--------------------------------------------------------------------------+
153|op_rw_prepare_latency | Latency of read-modify-write operations (excluding queue time |
154| | and wait for finished) |
155+------------------------+--------------------------------------------------------------------------+
156|op_before_queue_op_lat | Latency of IO before calling queue (before really queue into ShardedOpWq)|
157| | op_before_dequeue_op_lat |
158+------------------------+--------------------------------------------------------------------------+
159|op_before_dequeue_op_lat| Latency of IO before calling dequeue_op(already dequeued and get PG lock)|
160+------------------------+--------------------------------------------------------------------------+
161
162Latency counters are measured in microseconds unless otherwise specified in the description.
163