]> git.proxmox.com Git - ceph.git/blame - ceph/doc/mgr/influx.rst
import 15.2.0 Octopus source
[ceph.git] / ceph / doc / mgr / influx.rst
CommitLineData
3efd9988 1=============
11fdf7f2 2Influx Module
3efd9988
FG
3=============
4
11fdf7f2 5The influx module continuously collects and sends time series data to an
3efd9988
FG
6influxdb database.
7
11fdf7f2 8The influx module was introduced in the 13.x *Mimic* release.
3efd9988
FG
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
11fdf7f2 39 ceph config set mgr mgr/influx/<key> <value>
3efd9988
FG
40
41
42The most important settings are ``hostname``, ``username`` and ``password``.
43For example, a typical configuration might look like this:
44
45::
46
11fdf7f2
TL
47 ceph config set mgr mgr/influx/hostname influx.mydomain.com
48 ceph config set mgr mgr/influx/username admin123
49 ceph config set mgr mgr/influx/password p4ssw0rd
3efd9988
FG
50
51Additional optional configuration settings are:
52
11fdf7f2 53:interval: Time between reports to InfluxDB. Default 30 seconds.
3efd9988
FG
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
11fdf7f2
TL
58:threads: How many worker threads should be spawned for sending data to InfluxDB. Default is 5
59:batch_size: How big batches of data points should be when sending to InfluxDB. Default is 5000
3efd9988
FG
60
61---------
62Debugging
63---------
64
11fdf7f2 65By default, a few debugging statements as well as error statements have been set to print in the log files. Users can add more if necessary.
3efd9988
FG
66To make use of the debugging option in the module:
67
68- Add this to the ceph.conf file.::
69
70 [mgr]
71 debug_mgr = 20
72
9f95a23c 73- Use this command ``ceph influx self-test``.
3efd9988
FG
74- Check the log files. Users may find it easier to filter the log files using *mgr[influx]*.
75
76--------------------
77Interesting counters
78--------------------
79
80The following tables describe a subset of the values output by
81this module.
82
83^^^^^
84Pools
85^^^^^
86
87+---------------+-----------------------------------------------------+
88|Counter | Description |
89+===============+=====================================================+
11fdf7f2 90|stored | Bytes stored in the pool not including copies |
3efd9988
FG
91+---------------+-----------------------------------------------------+
92|max_avail | Max available number of bytes in the pool |
93+---------------+-----------------------------------------------------+
94|objects | Number of objects in the pool |
95+---------------+-----------------------------------------------------+
96|wr_bytes | Number of bytes written in the pool |
97+---------------+-----------------------------------------------------+
98|dirty | Number of bytes dirty in the pool |
99+---------------+-----------------------------------------------------+
100|rd_bytes | Number of bytes read in the pool |
101+---------------+-----------------------------------------------------+
11fdf7f2 102|stored_raw | Bytes used in pool including copies made |
3efd9988
FG
103+---------------+-----------------------------------------------------+
104
105^^^^
106OSDs
107^^^^
108
109+------------+------------------------------------+
110|Counter | Description |
111+============+====================================+
112|op_w | Client write operations |
113+------------+------------------------------------+
114|op_in_bytes | Client operations total write size |
115+------------+------------------------------------+
116|op_r | Client read operations |
117+------------+------------------------------------+
118|op_out_bytes| Client operations total read size |
119+------------+------------------------------------+
120
121
122+------------------------+--------------------------------------------------------------------------+
123|Counter | Description |
124+========================+==========================================================================+
125|op_wip | Replication operations currently being processed (primary) |
126+------------------------+--------------------------------------------------------------------------+
127|op_latency | Latency of client operations (including queue time) |
128+------------------------+--------------------------------------------------------------------------+
129|op_process_latency | Latency of client operations (excluding queue time) |
130+------------------------+--------------------------------------------------------------------------+
131|op_prepare_latency | Latency of client operations (excluding queue time and wait for finished)|
132+------------------------+--------------------------------------------------------------------------+
133|op_r_latency | Latency of read operation (including queue time) |
134+------------------------+--------------------------------------------------------------------------+
135|op_r_process_latency | Latency of read operation (excluding queue time) |
136+------------------------+--------------------------------------------------------------------------+
137|op_w_in_bytes | Client data written |
138+------------------------+--------------------------------------------------------------------------+
139|op_w_latency | Latency of write operation (including queue time) |
140+------------------------+--------------------------------------------------------------------------+
141|op_w_process_latency | Latency of write operation (excluding queue time) |
142+------------------------+--------------------------------------------------------------------------+
143|op_w_prepare_latency | Latency of write operations (excluding queue time and wait for finished) |
144+------------------------+--------------------------------------------------------------------------+
145|op_rw | Client read-modify-write operations |
146+------------------------+--------------------------------------------------------------------------+
147|op_rw_in_bytes | Client read-modify-write operations write in |
148+------------------------+--------------------------------------------------------------------------+
149|op_rw_out_bytes | Client read-modify-write operations read out |
150+------------------------+--------------------------------------------------------------------------+
151|op_rw_latency | Latency of read-modify-write operation (including queue time) |
152+------------------------+--------------------------------------------------------------------------+
153|op_rw_process_latency | Latency of read-modify-write operation (excluding queue time) |
154+------------------------+--------------------------------------------------------------------------+
155|op_rw_prepare_latency | Latency of read-modify-write operations (excluding queue time |
156| | and wait for finished) |
157+------------------------+--------------------------------------------------------------------------+
158|op_before_queue_op_lat | Latency of IO before calling queue (before really queue into ShardedOpWq)|
159| | op_before_dequeue_op_lat |
160+------------------------+--------------------------------------------------------------------------+
161|op_before_dequeue_op_lat| Latency of IO before calling dequeue_op(already dequeued and get PG lock)|
162+------------------------+--------------------------------------------------------------------------+
163
164Latency counters are measured in microseconds unless otherwise specified in the description.
165