blob: 9c8357130f9ab3be103a928173e0b3a4e30821e9 (
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
|
<!--
---
title: "Exporting metrics to external databases (experimental)"
custom_edit_url: https://github.com/netdata/netdata/edit/master/exporting/README.md
---
-->
# Exporting metrics to external databases (experimental)
The exporting engine is an update for the former [backends](/backends/README.md). It's still work in progress. It has a
modular structure and supports metric exporting via multiple exporting connector instances at the same time. You can
have different update intervals and filters configured for every exporting connector instance. The exporting engine has
its own configuration file `exporting.conf`. Configuration is almost similar to [backends](/backends/README.md#configuration).
The only difference is that the type of a connector should be specified in a section name before a colon and a name after
the colon. At the moment only four types of connectors are supported: `graphite`, `json`, `opentsdb`, `opentsdb:http`.
An example configuration:
```conf
[exporting:global]
enabled = yes
[graphite:my_instance1]
enabled = yes
destination = localhost:2003
data source = sum
update every = 5
send charts matching = system.load
[json:my_instance2]
enabled = yes
destination = localhost:5448
data source = as collected
update every = 2
send charts matching = system.active_processes
[opentsdb:my_instance3]
enabled = yes
destination = localhost:4242
data source = sum
update every = 10
send charts matching = system.cpu
[opentsdb:http:my_instance4]
enabled = yes
destination = localhost:4243
data source = average
update every = 3
send charts matching = system.active_processes
```
[](<>)
|
