@cryptotaxi247 / netdata-1 / commits / 93527e74e

updated info

Costa Tsaousis (ktsaou) committed Feb 23, 2017 at 00:52 UTC 93527e74eabb9acab84a6ae26baa7e5c49219dff
1 file changed +43 -15
conf.d/aggregated_hosts.conf
+43 -15
@@ -1,31 +1,58 @@
1 # netdata configuration for aggregating data from remote hosts
2 #
3 -# 1. You need an API key: API_KEY_GENERATED_BY_UUIDGEN
3 +# -----------------------------------------------------------------------------
4 +# 1. SLAVE NETDATA - THE ONE THAT WILL BE SENDING METRICS
5 +#
6 +# In /etc/netdata/netdata.conf you have a configuration like this:
7 +#
8 +# [stream]
9 +#
10 +# # enable or disable sending metrics.
11 +# # default: no
12 +# enabled = yes
13 +#
14 +# # when set to yes, the slave netdata will not start
15 +# # its web server and will not maintain a database.
16 +# # when set to yes, the slave netdata will be just a metrics collector.
17 +# # default: yes
18 +# exclusive = yes
19 +#
20 +# # one or more netdata hosts to send metrics to.
21 +# # only one will get them, the first available.
22 +# stream metrics to = HOST1:PORT1 HOST2:PORT2 ...
23 +#
24 +# # the API key to use, to authorize ourselves
25 +# api key = API_KEY_GENERATED_BY_UUIDGEN
26 +#
27 +# -----------------------------------------------------------------------------
28 +# 2. MASTER NETDATA - THE ONE THAT WILL BE RECEIVING METRICS
29 +#
30 +# You need an API key: API_KEY_GENERATED_BY_UUIDGEN
31 +# This key should be specified at the master and the slave netdata servers.
32 #
33 # You can generate one with the command: uuidgen
6 -# You can add many API key sections, for different API keys
34 +# You can add many API key sections below, for each API key.
35 +#
36 +# You can have one API key per slave, or the same API key for all slaves.
37 +# Each slave will automatically create its own virtual host at the master
38 +# even if all slaves use the same API key.
39 #
8 -# 2. All options below are used in this order:
40 +# All options below are used in this order:
41 #
42 # a) MACHINE_GUID (settings for each machine)
43 # b) API_KEY (settings for the API key)
44 # c) this netdata defaults (as in netdata.conf)
45 #
14 -# You can combine the above (the more specific will be used).
15 -#
16 -# 3. At the remote host that will be sending metrics, you need
17 -# to add in netdata.conf, the following:
18 -#
19 -# [global]
20 -# central netdata to send all data = 10.11.12.1:19999
21 -# central netdata api key = API_KEY_GENERATED_BY_UUIDGEN
22 -#
23 -# Of course, the same API_KEY_GENERATED_BY_UUIDGEN key must
24 -# given there (the remote host) and here (the central netdata).
46 +# You can combine the above (the more specific setting will be used).
47 #
48 # -----------------------------------------------------------------------------
49
50 +# API key authentication
51 +# If the key is not listed here, it will not be able to connect.
52 +
53 [API_KEY_GENERATED_BY_UUIDGEN]
54 + # Default settings for the API key
55 +
56 # You can disable the API key, by setting this to: no
57 # The default (for unknown API keys) is also: no
58 # enabled = yes
@@ -39,7 +66,8 @@
66 # The default memory mode to be used for all hosts using this API key.
67 # You can also set it per host below.
68 # If you don't set it here, the memory mode of the central netdata
42 - # will be used
69 + # will be used.
70 + # Valid modes: save (load/save db), map (like swap), ram (no disk)
71 # default memory mode = save
72
73 # Shall we enable health monitoring for the hosts using this API key?