Ga (#4938)

CODE_OF_CONDUCT.md

+2

@@ -72,3 +72,5 @@ available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.ht

72

73 [homepage]: https://www.contributor-covenant.org

74

75 +

76 +[]()

CONTRIBUTING.md

+2

@@ -134,3 +134,5 @@ We also have a series of automated checks running, such as linters to check code

134

135 One special type of automated check is the "WIP" check. You may add "[WIP]" to the title of the PR, to tell us that the particular request is "Work In Progress" and should not be merged. You're still not done with it, you created it to get some feedback. When you're ready to get the final approvals and get it merged, just remove the "[WIP]" string from the title of your PR and the "WIP" check will pass.

136

137 +

138 +[]()

CONTRIBUTORS.md

+2

@@ -121,3 +121,5 @@ username|name|email (optional)

121 @pohzipohzi|Poh Zi How

122 @vladmovchan|Vladyslav Movchan|vladislav.movchan@gmail.com

123 @gmosx|George Moschovitis

124 +

125 +[]()

README.md

+1

@@ -492,3 +492,4 @@ You can also find netdata on:

492 netdata is [GPLv3+](LICENSE).

493

494 Netdata re-distributes other open-source tools and libraries. Please check the [third party licenses](REDISTRIBUTED.md).

495 +

REDISTRIBUTED.md

+2

@@ -199,3 +199,5 @@ connectivity is not available.

199

200 Copyright 2014, 2015, 2016 Ori Livneh <ori@wikimedia.org>

201 [Apache-2.0](http://www.apache.org/licenses/LICENSE-2.0)

202 +

203 +[]()

backends/README.md

+2

@@ -196,3 +196,5 @@ netdata adds 4 alarms:

196

197 

198

199 +

200 +[]()

backends/WALKTHROUGH.md

+2

@@ -290,3 +290,5 @@ automatically begins to scrape them. Once achieved you do not have to think

290 about the monitoring system until Prometheus cannot keep up with your scale.

291 Once this happens there are options presented in the Prometheus documentation

292 for solving this. Hope this was helpful, happy monitoring.

293 +

294 +[]()

backends/prometheus/README.md

+2

@@ -378,3 +378,5 @@ It can also be changed from the URL, by appending `&prefix=netdata`.

378 When the data source is set to `average` or `sum`, netdata remembers the last access of each client accessing prometheus metrics and uses this last access time to respond with the `average` or `sum` of all the entries in the database since that. This means that prometheus servers are not losing data when they access netdata with data source = `average` or `sum`.

379

380 To uniquely identify each prometheus server, netdata uses the IP of the client accessing the metrics. If however the IP is not good enough for identifying a single prometheus server (e.g. when prometheus servers are accessing netdata through a web proxy, or when multiple prometheus servers are NATed to a single IP), each prometheus may append `&server=NAME` to the URL. This `NAME` is used by netdata to uniquely identify each prometheus server and keep track of its last access time.

381 +

382 +[]()

collectors/README.md

+2

@@ -116,3 +116,5 @@ The best way to find your way through this, is to examine what other similar plu

116

117 **External plugins** use the API and are managed by [plugins.d](plugins.d/).

118

119 +

120 +[]()

collectors/apps.plugin/README.md

+2

@@ -370,3 +370,5 @@ It is even trickier, because walking through the entire process tree takes some

370 if you sum the CPU utilization of all processes, you might have more CPU time than the reported

371 total cpu time of the system. netdata solves this, by adapting the per process cpu utilization to

372 the total of the system. [Netdata adds charts that document this normalization](https://london.my-netdata.io/default.html#menu_netdata_submenu_apps_plugin).

373 +

374 +[]()

collectors/cgroups.plugin/README.md

+2

@@ -185,3 +185,5 @@ So, when a network interface or container stops, netdata might log a few errors

185 6. obsolete charts will be removed from memory, 1 hour after the last user viewed them (configurable with `[global].cleanup obsolete charts after seconds = 3600` (at netdata.conf).

186 7. when obsolete charts are removed from memory they are also deleted from disk (configurable with `[global].delete obsolete charts files = yes`)

187

188 +

189 +[]()

collectors/charts.d.plugin/README.md

+2

@@ -191,3 +191,5 @@ This is what you need to do:

191 Execute the above in this order, since netdata will (by default) attempt to start new plugins soon after they are

192 created in `/usr/libexec/netdata/plugins.d/`.

193

194 +

195 +[]()

collectors/charts.d.plugin/ap/README.md

+2

@@ -82,3 +82,5 @@ To edit this file on your system run `/etc/netdata/edit-config charts.d/ap.conf`

82 ## Auto-detection

83

84 The plugin is able to auto-detect if you are running access points on your linux box.

85 +

86 +[]()

collectors/charts.d.plugin/apache/README.md

+2

@@ -125,3 +125,5 @@ curl "http://127.0.0.1:80/server-status?auto"

125 netdata will be able to do it too.

126

127 Notice: You may need to have the default `000-default.conf ` website enabled in order for the status mod to work.

128 +

129 +[]()

collectors/charts.d.plugin/apcupsd/README.md

+2

@@ -3,3 +3,5 @@

3 *Under construction*

4

5 Collects UPS metrics

6 +

7 +[]()

collectors/charts.d.plugin/cpu_apps/README.md

+2

@@ -2,3 +2,5 @@

2

3 > THIS MODULE IS OBSOLETE.

4 > USE [APPS.PLUGIN](../../apps.plugin).

5 +

6 +[]()

collectors/charts.d.plugin/cpufreq/README.md

+2

@@ -2,3 +2,5 @@

2

3 > THIS MODULE IS OBSOLETE.

4 > USE THE [PROC PLUGIN](../../proc.plugin) - IT SUPPORTS MULTIPLE JOBS AND IT IS MORE EFFICIENT

5 +

6 +[]()

collectors/charts.d.plugin/example/README.md

+2

@@ -2,3 +2,5 @@

2

3 This is just an example charts.d data collector.

4

5 +

6 +[]()

collectors/charts.d.plugin/exim/README.md

+2

@@ -2,3 +2,5 @@

2

3 > THIS MODULE IS OBSOLETE.

4 > USE [THE PYTHON ONE](../../python.d.plugin/exim) - IT SUPPORTS MULTIPLE JOBS AND IT IS MORE EFFICIENT

5 +

6 +[]()

collectors/charts.d.plugin/hddtemp/README.md

+2

@@ -26,3 +26,5 @@ hddtemp_disks=()

26 ```

27

28 ---

29 +

30 +[]()

collectors/charts.d.plugin/libreswan/README.md

+2

@@ -40,3 +40,5 @@ netdata ALL = (root) NOPASSWD: /sbin/ipsec whack --trafficstatus

40 Make sure the path `/sbin/ipsec` matches your setup (execute `which ipsec` to find the right path).

41

42 ---

43 +

44 +[]()

collectors/charts.d.plugin/load_average/README.md

+2

@@ -2,3 +2,5 @@

2

3 > THIS MODULE IS OBSOLETE.

4 > THE NETDATA DAEMON COLLECTS LOAD AVERAGE BY ITSELF

5 +

6 +[]()

collectors/charts.d.plugin/mem_apps/README.md

+2

@@ -2,3 +2,5 @@

2

3 > THIS MODULE IS OBSOLETE.

4 > USE [APPS.PLUGIN](../../apps.plugin).

5 +

6 +[]()

collectors/charts.d.plugin/mysql/README.md

+2

@@ -79,3 +79,5 @@ If no configuration is given, the plugin will attempt to connect to mysql server

79

80

81 ---

82 +

83 +[]()

collectors/charts.d.plugin/nginx/README.md

+2

@@ -2,3 +2,5 @@

2

3 > THIS MODULE IS OBSOLETE.

4 > USE [THE PYTHON ONE](../../python.d.plugin/nginx) - IT SUPPORTS MULTIPLE JOBS AND IT IS MORE EFFICIENT

5 +

6 +[]()

collectors/charts.d.plugin/nut/README.md

+2

@@ -57,3 +57,5 @@ nut_update_every=2

57 ```

58

59 ---

60 +

61 +[]()

collectors/charts.d.plugin/opensips/README.md

+2

@@ -3,3 +3,5 @@

3 *Under construction*

4

5 Collects OpenSIPS metrics

6 +

7 +[]()

collectors/charts.d.plugin/phpfpm/README.md

+2

@@ -2,3 +2,5 @@

2

3 > THIS MODULE IS OBSOLETE.

4 > USE [THE PYTHON ONE](../../python.d.plugin/phpfpm) - IT SUPPORTS MULTIPLE JOBS AND IT IS MORE EFFICIENT

5 +

6 +[]()

collectors/charts.d.plugin/postfix/README.md

+2

@@ -24,3 +24,5 @@ postfix_update_every=15

24 ```

25

26 ---

27 +

28 +[]()

collectors/charts.d.plugin/sensors/README.md

+2

@@ -51,3 +51,5 @@ sensors_excluded=()

51 ```

52

53 ---

54 +

55 +[]()

collectors/charts.d.plugin/squid/README.md

+2

@@ -63,3 +63,5 @@ squid_update_every=5

63 ```

64

65 ---

66 +

67 +[]()

collectors/charts.d.plugin/tomcat/README.md

+2

@@ -2,3 +2,5 @@

2

3 > THIS MODULE IS OBSOLETE.

4 > USE [THE PYTHON ONE](../../python.d.plugin/tomcat) - IT SUPPORTS MULTIPLE JOBS AND IT IS MORE EFFICIENT

5 +

6 +[]()

collectors/checks.plugin/README.md

+2

@@ -1,3 +1,5 @@

1 # checks.plugin

2

3 A debugging plugin (by default it is disabled)

4 +

5 +[]()

collectors/diskspace.plugin/README.md

+2

@@ -4,3 +4,5 @@ This plugin monitors the disk space usage of mounted disks, under Linux.

4

5 > for disks performance monitoring, see the `proc` plugin, [here](../proc.plugin/#monitoring-disks)

6

7 +

8 +[]()

collectors/fping.plugin/README.md

+2

@@ -94,3 +94,5 @@ That's it. netdata will detect the new plugin and start it.

94

95 You can name the new plugin any name you like.

96 Just make sure the plugin and the configuration file have the same name.

97 +

98 +[]()

collectors/freebsd.plugin/README.md

+2

@@ -1,3 +1,5 @@

1 # freebsd.plugin

2

3 Collects resource usage and performance data on FreeBSD systems

4 +

5 +[]()

collectors/freeipmi.plugin/README.md

+2

@@ -180,3 +180,5 @@ If you need to disable IPMI for netdata, edit `/etc/netdata/netdata.conf` and se

180 [plugins]

181 freeipmi = no

182 ```

183 +

184 +[]()

collectors/idlejitter.plugin/README.md

+2

@@ -11,3 +11,5 @@ This number is useful:

11

12 1. in real-time environments, when the CPU jitter can affect the quality of the service (like VoIP media gateways).

13 2. in cloud infrastructure, at can pause the VM or container for a small duration to perform operations at the host.

14 +

15 +[]()

collectors/macos.plugin/README.md

+2

@@ -1,3 +1,5 @@

1 # macos.plugin

2

3 Collects resource usage and performance data on MacOS systems

4 +

5 +[]()

collectors/nfacct.plugin/README.md

+2

@@ -8,3 +8,5 @@ We have to move the code to an external plugin to setuid just the plugin not the

8 You can build netdata with it to test it though.

9 Just run `./configure` (or `netdata-installer.sh`) with the option `--enable-plugin-nfacct` (and any other options you may need).

10 Remember, you have to tell netdata you want it to run as `root` for this plugin to work.

11 +

12 +[]()

collectors/node.d.plugin/README.md

+2

@@ -230,3 +230,5 @@ The `service` object defines a set of functions to allow you send information to

230

231 *FIXME: document an operational node.d.plugin data collector - the best example is the

232 [snmp collector](snmp/snmp.node.js)*

233 +

234 +[]()

collectors/node.d.plugin/fronius/README.md

+2

@@ -118,3 +118,5 @@ The output of /solar_api/v1/GetPowerFlowRealtimeData.fcgi looks like this:

118 }

119 }

120 ```

121 +

122 +[]()

collectors/node.d.plugin/named/README.md

+2

@@ -340,3 +340,5 @@ Verify it works by running the following command (the collector is written in no

340 curl "http://localhost:8888/json/v1/server"

341 ```

342

343 +

344 +[]()

collectors/node.d.plugin/sma_webbox/README.md

+2

@@ -23,3 +23,5 @@ The module supports any number of name servers, like this:

23 ]

24 }

25 ```

26 +

27 +[]()

collectors/node.d.plugin/snmp/README.md

+2

@@ -355,3 +355,5 @@ This switch has a very slow SNMP processors. To respond, it needs about 8 second

355 ]

356 }

357 ```

358 +

359 +[]()

collectors/node.d.plugin/stiebeleltron/README.md

+2

@@ -503,3 +503,5 @@ The charts are being generated using the configuration below. So if your install

503 ]

504 }

505 ```

506 +

507 +[]()

collectors/plugins.d/README.md

+2

@@ -471,3 +471,5 @@ There are a few rules for writing plugins properly:

471

472 4. If possible, try to autodetect if your plugin should be enabled, without any configuration.

473

474 +

475 +[]()

collectors/proc.plugin/README.md

+2

@@ -272,3 +272,5 @@ Example image:

272 

273

274 See Linux Anti-DDoS in action at: **[netdata demo site (with SYNPROXY enabled)](https://registry.my-netdata.io/#menu_netfilter_submenu_synproxy)**

275 +

276 +[]()

collectors/python.d.plugin/README.md

+2

@@ -221,3 +221,5 @@ At minimum, to be buildable and testable, the PR needs to include:

221 * A line for the plugin in `python.d/Makefile.am` under `dist_python_DATA`.

222 * A line for the plugin configuration file in `conf.d/Makefile.am`, under `dist_pythonconfig_DATA`

223 * Optionally, chart information in `web/dashboard_info.js`. This generally involves specifying a name and icon for the section, and may include descriptions for the section or individual charts.

224 +

225 +[]()

collectors/python.d.plugin/adaptec_raid/README.md

+2

@@ -44,3 +44,5 @@ adaptec_raid: yes

44 

45

46 ---

47 +

48 +[]()

collectors/python.d.plugin/apache/README.md

+2

@@ -55,3 +55,5 @@ remote:

55 Without configuration, module attempts to connect to `http://localhost/server-status?auto`

56

57 ---

58 +

59 +[]()

collectors/python.d.plugin/beanstalk/README.md

+2

@@ -101,3 +101,5 @@ port : 11300

101 If no configuration is given, module will attempt to connect to beanstalkd on `127.0.0.1:11300` address

102

103 ---

104 +

105 +[]()

collectors/python.d.plugin/bind_rndc/README.md

+2

@@ -58,3 +58,5 @@ local:

58 If no configuration is given, module will attempt to read named.stats file at `/var/log/bind/named.stats`

59

60 ---

61 +

62 +[]()

collectors/python.d.plugin/boinc/README.md

+2

@@ -26,3 +26,5 @@ remote:

26 ```

27

28 ---

29 +

30 +[]()

collectors/python.d.plugin/ceph/README.md

+2

@@ -30,3 +30,5 @@ local:

30 ```

31

32 ---

33 +

34 +[]()

collectors/python.d.plugin/chrony/README.md

+2

@@ -29,3 +29,5 @@ local:

29 ```

30

31 ---

32 +

33 +[]()

collectors/python.d.plugin/couchdb/README.md

+2

@@ -33,3 +33,5 @@ local:

33 ```

34

35 ---

36 +

37 +[]()

collectors/python.d.plugin/cpufreq/README.md

+2

@@ -33,3 +33,5 @@ If no configuration is given, module will search for cpufreq files in `/sys/devi

33 Directory is also prefixed with `NETDATA_HOST_PREFIX` if specified.

34

35 ---

36 +

37 +[]()

collectors/python.d.plugin/cpuidle/README.md

+2

@@ -9,3 +9,5 @@ It produces one stacked chart per CPU, showing the percentage of time spent in

9 each state.

10

11 ---

12 +

13 +[]()

collectors/python.d.plugin/dns_query_time/README.md

+2

@@ -8,3 +8,5 @@ This module provides DNS query time statistics.

8 It produces one aggregate chart or one chart per DNS server, showing the query time.

9

10 ---

11 +

12 +[]()

collectors/python.d.plugin/dnsdist/README.md

+2

@@ -52,3 +52,5 @@ localhost:

52 ```

53

54 ---

55 +

56 +[]()

collectors/python.d.plugin/dockerd/README.md

+2

@@ -24,3 +24,5 @@ Following charts are drawn:

24 ```

25

26 ---

27 +

28 +[]()

collectors/python.d.plugin/dovecot/README.md

+2

@@ -71,3 +71,5 @@ localsocket:

71 If no configuration is given, module will attempt to connect to dovecot using unix socket localized in `/var/run/dovecot/stats`

72

73 ---

74 +

75 +[]()

collectors/python.d.plugin/elasticsearch/README.md

+2

@@ -58,3 +58,5 @@ local:

58 If no configuration is given, module will fail to run.

59

60 ---

61 +

62 +[]()

collectors/python.d.plugin/example/README.md

+2

@@ -1,3 +1,5 @@

1 # example

2

3 An example python data collection module.

4 +

5 +[]()

collectors/python.d.plugin/exim/README.md

+2

@@ -11,3 +11,5 @@ It produces only one chart:

11 Configuration is not needed.

12

13 ---

14 +

15 +[]()

collectors/python.d.plugin/fail2ban/README.md

+2

@@ -21,3 +21,5 @@ If no configuration is given, module will attempt to read log file at `/var/log/

21 If conf file is not found default jail is `ssh`.

22

23 ---

24 +

25 +[]()

collectors/python.d.plugin/freeradius/README.md

+2

@@ -68,3 +68,5 @@ To do this, create a link from the sites-enabled directory to the status file in

68 and restart/reload your FREERADIUS server.

69

70 ---

71 +

72 +[]()

collectors/python.d.plugin/go_expvar/README.md

+2

@@ -273,3 +273,5 @@ The images below show how do the final charts in netdata look.

273

274 

275

276 +

277 +[]()

collectors/python.d.plugin/haproxy/README.md

+2

@@ -47,3 +47,5 @@ via_socket:

47 If no configuration is given, module will fail to run.

48

49 ---

50 +

51 +[]()

collectors/python.d.plugin/hddtemp/README.md

+2

@@ -20,3 +20,5 @@ port: 7634

20 If no configuration is given, module will attempt to connect to hddtemp daemon on `127.0.0.1:7634` address

21

22 ---

23 +

24 +[]()

collectors/python.d.plugin/httpcheck/README.md

+2

@@ -39,3 +39,5 @@ server:

39 response time is low and should be used as reference only.

40

41 ---

42 +

43 +[]()

collectors/python.d.plugin/icecast/README.md

+2

@@ -24,3 +24,5 @@ remote:

24 Without configuration, module attempts to connect to `http://localhost:8443/status-json.xsl`

25

26 ---

27 +

28 +[]()

collectors/python.d.plugin/ipfs/README.md

+2

@@ -23,3 +23,5 @@ localhost:

23

24 ---

25

26 +

27 +[]()

collectors/python.d.plugin/isc_dhcpd/README.md

+2

@@ -32,3 +32,5 @@ In case of python2 you need to install `py2-ipaddress` to make plugin work.

32 The module will not work If no configuration is given.

33

34 ---

35 +

36 +[]()

collectors/python.d.plugin/linux_power_supply/README.md

+2

@@ -65,3 +65,5 @@ the corresponding `min` or `empty`, which will then always read as zero.

65 This way, alerts which match on these will still work.

66

67 ---

68 +

69 +[]()

collectors/python.d.plugin/litespeed/README.md

+2

@@ -45,3 +45,5 @@ local:

45 If no configuration is given, module will use "/tmp/lshttpd/".

46

47 ---

48 +

49 +[]()

collectors/python.d.plugin/logind/README.md

+2

@@ -52,3 +52,5 @@ is currently disabled by default, and needs to be explicitly enabled in

52 `/etc/netdata/python.d.conf` before it will run.

53

54 ---

55 +

56 +[]()

collectors/python.d.plugin/mdstat/README.md

+2

@@ -29,3 +29,5 @@ It produces:

29 No configuration is needed.

30

31 ---

32 +

33 +[]()

collectors/python.d.plugin/megacli/README.md

+2

@@ -46,3 +46,5 @@ do_battery: yes

46 ```

47

48 ---

49 +

50 +[]()

collectors/python.d.plugin/memcached/README.md

+2

@@ -67,3 +67,5 @@ localtcpip:

67 If no configuration is given, module will attempt to connect to memcached instance on `127.0.0.1:11211` address.

68

69 ---

70 +

71 +[]()

collectors/python.d.plugin/mongodb/README.md

+2

@@ -166,3 +166,5 @@ local:

166 If no configuration is given, module will attempt to connect to mongodb daemon on `127.0.0.1:27017` address

167

168 ---

169 +

170 +[]()

collectors/python.d.plugin/monit/README.md

+2

@@ -31,3 +31,5 @@ local:

31 If no configuration is given, module will attempt to connect to monit as `http://localhost:2812`.

32

33 ---

34 +

35 +[]()

collectors/python.d.plugin/mysql/README.md

+2

@@ -86,3 +86,5 @@ remote:

86 If no configuration is given, module will attempt to connect to mysql server via unix socket at `/var/run/mysqld/mysqld.sock` without password and with username `root`

87

88 ---

89 +

90 +[]()

collectors/python.d.plugin/nginx/README.md

+2

@@ -42,3 +42,5 @@ local:

42 Without configuration, module attempts to connect to `http://localhost/stub_status`

43

44 ---

45 +

46 +[]()

collectors/python.d.plugin/nginx_plus/README.md

+2

@@ -123,3 +123,5 @@ local:

123 Without configuration, module fail to start.

124

125 ---

126 +

127 +[]()

collectors/python.d.plugin/nsd/README.md

+2

@@ -52,3 +52,5 @@ It produces:

52 Configuration is not needed.

53

54 ---

55 +

56 +[]()

collectors/python.d.plugin/ntpd/README.md

+2

@@ -69,3 +69,5 @@ otherhost:

69 If no configuration is given, module will attempt to connect to `ntpd` on `::1:123` or `127.0.0.1:123` and show charts for the systemvars. Use `show_peers: yes` to also show the charts for configured peers. Local peers in the range `127.0.0.0/8` are hidden by default, use `peer_filter: ''` to show all peers.

70

71 ---

72 +

73 +[]()

collectors/python.d.plugin/nvidia_smi/README.md

+2 -1

@@ -36,4 +36,5 @@ Sample:

36

37 ```yaml

38 poll_seconds: 1

39 -```

\ No newline at end of file

39 +```

40 +[]()

collectors/python.d.plugin/openldap/README.md

+2

@@ -55,3 +55,5 @@ openldap:

55 ```

56

57 ---

58 +

59 +[]()

collectors/python.d.plugin/ovpn_status_log/README.md

+2

@@ -30,3 +30,5 @@ default

30 ```

31

32 ---

33 +

34 +[]()

collectors/python.d.plugin/phpfpm/README.md

+2

@@ -37,3 +37,5 @@ local:

37 Without configuration, module attempts to connect to `http://localhost/status`

38

39 ---

40 +

41 +[]()

collectors/python.d.plugin/portcheck/README.md

+2

@@ -33,3 +33,5 @@ server:

33 * Currently, the accuracy of the latency is low and should be used as reference only.

34

35 ---

36 +

37 +[]()

collectors/python.d.plugin/postfix/README.md

+2

@@ -13,3 +13,5 @@ It produces only two charts:

13 Configuration is not needed.

14

15 ---

16 +

17 +[]()

collectors/python.d.plugin/postgres/README.md

+2

@@ -66,3 +66,5 @@ tcp:

66 When no configuration file is found, module tries to connect to TCP/IP socket: `localhost:5432`.

67

68 ---

69 +

70 +[]()

collectors/python.d.plugin/powerdns/README.md

+2

@@ -75,3 +75,5 @@ local:

75 ```

76

77 ---

78 +

79 +[]()

collectors/python.d.plugin/proxysql/README.md

+2

@@ -60,3 +60,5 @@ tcpipv4:

60 If no configuration is given, module will fail to run.

61

62 ---

63 +

64 +[]()

collectors/python.d.plugin/puppet/README.md

+2

@@ -43,3 +43,5 @@ When no configuration is given, module uses `https://fqdn.example.com:8140`.

43 to default PuppetDB configuration though.

44

45 ---

46 +

47 +[]()

collectors/python.d.plugin/rabbitmq/README.md

+2

@@ -54,3 +54,5 @@ socket:

54 When no configuration file is found, module tries to connect to: `localhost:15672`.

55

56 ---

57 +

58 +[]()

collectors/python.d.plugin/redis/README.md

+2

@@ -40,3 +40,5 @@ localhost:

40 When no configuration file is found, module tries to connect to TCP/IP socket: `localhost:6379`.

41

42 ---

43 +

44 +[]()

collectors/python.d.plugin/rethinkdbs/README.md

+2

@@ -32,3 +32,5 @@ localhost:

32 When no configuration file is found, module tries to connect to `127.0.0.1:28015`.

33

34 ---

35 +

36 +[]()

collectors/python.d.plugin/retroshare/README.md

+2

@@ -1 +1,3 @@

1 # retroshare

2 +

3 +[]()

collectors/python.d.plugin/samba/README.md

+2

@@ -65,3 +65,5 @@ samba: yes

65 ```

66

67 ---

68 +

69 +[]()

collectors/python.d.plugin/sensors/README.md

+2

@@ -15,3 +15,5 @@ We are tracking such cases in issue [#827](https://github.com/netdata/netdata/is

15 Please join this discussion for help.

16

17 ---

18 +

19 +[]()

collectors/python.d.plugin/smartd_log/README.md

+2

@@ -99,3 +99,5 @@ local:

99 If no configuration is given, module will attempt to read log files in `/var/log/smartd/` directory.

100

101 ---

102 +

103 +[]()

collectors/python.d.plugin/spigotmc/README.md

+2

@@ -20,3 +20,5 @@ password: pass

20 By default, a connection to port 25575 on the local system is attempted with an empty password.

21

22 ---

23 +

24 +[]()

collectors/python.d.plugin/springboot/README.md

+2

@@ -120,3 +120,5 @@ You can disable the default charts by set `defaults.<chart-id>: false`.

120 The dimension name of extras charts should replace `.` to `_`.

121

122 Please check [springboot.conf](springboot.conf) for more examples.

123 +

124 +[]()

collectors/python.d.plugin/squid/README.md

+2

@@ -36,3 +36,5 @@ local:

36 Without any configuration module will try to autodetect where squid presents its `counters` data

37

38 ---

39 +

40 +[]()

collectors/python.d.plugin/tomcat/README.md

+2

@@ -31,3 +31,5 @@ Without configuration, module attempts to connect to `http://localhost:8080/mana

31 So it will probably fail.

32

33 ---

34 +

35 +[]()

collectors/python.d.plugin/tor/README.md

+2

@@ -44,3 +44,5 @@ For more options please read the manual.

44 Without configuration, module attempts to connect to `127.0.0.1:9051`.

45

46 ---

47 +

48 +[]()

collectors/python.d.plugin/traefik/README.md

+2

@@ -51,3 +51,5 @@ local:

51 Without configuration, module attempts to connect to `http://localhost:8080/health`.

52

53 ---

54 +

55 +[]()

collectors/python.d.plugin/unbound/README.md

+2

@@ -74,3 +74,5 @@ While it's a bit more complicated to set up correctly, it is recommended

74 that you use a UNIX socket as it provides far better performance.

75

76 ---

77 +

78 +[]()

collectors/python.d.plugin/uwsgi/README.md

+2

@@ -35,3 +35,5 @@ localhost:

35 ```

36

37 When no configuration file is found, module tries to connect to TCP/IP socket: `localhost:1717`.

38 +

39 +[]()

collectors/python.d.plugin/varnish/README.md

+2

@@ -67,3 +67,5 @@ It produces:

67 No configuration is needed.

68

69 ---

70 +

71 +[]()

collectors/python.d.plugin/w1sensor/README.md

+2

@@ -11,3 +11,5 @@ Charts are created dynamically based on the number of detected sensors.

11 For detailed configuration information please read [`w1sensor.conf`](w1sensor.conf) file.

12

13 ---

14 +

15 +[]()

collectors/python.d.plugin/web_log/README.md

+2

@@ -199,3 +199,5 @@ The column `minimum requests` state the minimum number of requests required for

199

200 [**netdata**](https://my-netdata.io/) alarms are user configurable. Sample config files can be found under directory `health/health.d` of the netdata github repository. So, even [`web_log` alarms can be adapted to your needs](../../../health/health.d/web_log.conf).

201

202 +

203 +[]()

collectors/statsd.plugin/README.md

+2

@@ -519,3 +519,5 @@ statsd "metric1:10|g" "metric2:10|c" ...

519 ```

520

521 The function is smart enough to call `nc` just once and pass all the metrics to it. It will also automatically switch to TCP if the metrics to send are above 1000 bytes.

522 +

523 +[]()

collectors/tc.plugin/README.md

+2

@@ -178,3 +178,5 @@ This is QoS from my home linux router. Check these features:

178 

179

180

181 +

182 +[]()

contrib/README.md

+2

@@ -56,3 +56,5 @@ The recommended way to upgrade netdata packages built from this

56 source is to remove the current package from your system, then

57 install the new package. Upgrading on wheezy is known to not

58 work cleanly; Jessie may behave as expected.

59 +

60 +[]()

contrib/sles11/README.md

+2

@@ -7,3 +7,5 @@ changes and additions for sles 11 backport, namely:

7 - patch for netdata python.d plugin to work with older python

8 - crude hack of notification script to work with bash 3 (email and syslog only, one destination,

9 see comments at the top)

10 +

11 +[]()

daemon/README.md

+2

@@ -516,3 +516,5 @@ valgrind $(which netdata) -D

516

517 netdata will start and it will be a lot slower. Now reproduce the crash and `valgrind` will dump on your console the stack trace. Open a new github issue and post the output.

518

519 +

520 +[]()

daemon/config/README.md

+2

@@ -142,3 +142,5 @@ External plugins that need additional configuration may support a dedicated file

142 ### Per chart configuration

143

144 In this section you will a separate subsection for each chart shown on the dashboard. You can control all aspects of a specific chart here. You can understand what each option does by reading [how charts are defined](../../collectors/plugins.d/#chart). If you don't know how to find the name of a chart, you can learn about it [here](../../docs/Charts.md).

145 +

146 +[]()

database/README.md

+2

@@ -204,3 +204,5 @@ Put the above lines in your boot sequence (`/etc/rc.local` or equivalent) to hav

204 Netdata will create charts for kernel memory de-duplication performance, like this:

205

206 

207 +

208 +[]()

diagrams/data_structures/README.md

+2

@@ -9,3 +9,5 @@ These are the main internal data structures of `netdata`. Created with `draw.io`

9 

10

11 

12 +

13 +[]()

docs/Add-more-charts-to-netdata.md

+2

@@ -427,3 +427,5 @@ application|language|notes|

427 :---------:|:------:|:----|

428 example|BASH<br/>Shell Script|Skeleton plugin in BASH.<br/><br/>DEPRECATED IN FAVOR OF THE PYTHON ONE. It is still supplied only as an example module to shell scripting plugins.<br/>&nbsp;<br/>netdata plugin: [charts.d.plugin](../collectors/charts.d.plugin#chartsdplugin)<br/>plugin module: [example.chart.sh](../collectors/charts.d.plugin/example)<br/>configuration file: [charts.d/example.conf](../collectors/charts.d.plugin/example)|

429 example|python<br/>v2 or v3|Skeleton plugin in Python.<br/>&nbsp;<br/>netdata plugin: [python.d.plugin](../collectors/python.d.plugin)<br/>plugin module: [example.chart.py](../collectors/python.d.plugin/example)<br/>configuration file: [python.d/example.conf](../collectors/python.d.plugin/example)|

430 +

431 +[]()

docs/Charts.md

+2

@@ -23,3 +23,5 @@ The reasoning behind calling these instances "families" is that different charts

23 A context is a grouping of identical charts, for each instance of the hardware or software monitored. For example, `health/health.d/net.conf` refers to four contexts: `net.drops`, `net.fifo`, `net.net`, `net.packets`. You can see the context of a chart if you hover over the date right above the dimensions of the chart. The line that appears shows you two things: the collector that produces the chart and the chart context.

24

25 For example, let's take the `net.packets` context. You will see on the dashboard as many charts with context net.packets as you have network interfaces (families). These charts will be named `net_packets.[family]`. For the example of the two interfaces `eth0` and `eth1`, you will see charts named `net_packets.eth0` and `net_packets.eth1`. Both of these charts show the exact same dimensions, but for different instances of a network interface.

26 +

27 +[]()

docs/Demo-Sites.md

+2

@@ -17,3 +17,5 @@ Singapore|**[singapore.my-netdata.io](https://singapore.my-netdata.io)**|[![Requ

17 Toronto (Canada)|**[toronto.my-netdata.io](https://toronto.my-netdata.io)**|[](https://toronto.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)

18

19 *Netdata dashboards are mobile and touch friendly.*

20 +

21 +[]()

docs/Donations-netdata-has-received.md

+2

@@ -21,3 +21,5 @@ Thank you!

21 **Do you want to donate?** We are thirsty for on-line services that can help us make netdata better. We also try to build a network of demo sites (VMs) that can help us show the full potential of netdata.

22

23 Please contact me at costa@tsaousis.gr.

24 +

25 +[]()

docs/GettingStarted.md

+2

@@ -178,3 +178,5 @@ and set `SEND_EMAIL="NO"`.

178 - Check [Health Monitoring](../health) for configuring your own alarms, or setting up alarm notifications.

179 - Check [Streaming](../streaming) for centralizing netdata metrics.

180 - Check [Backends](../backends) for long term archiving of netdata metrics to time-series databases.

181 +

182 +[]()

docs/Netdata-Security-and-Disclosure-Information.md

+2

@@ -35,3 +35,5 @@ As the security issue moves from triage, to identified fix, to release planning

35 ## Public Disclosure Timing

36

37 A public disclosure date is negotiated by the Netdata team and the bug submitter. We prefer to fully disclose the bug as soon as possible once a user mitigation is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. As a basic default, we expect report date to disclosure date to be on the order of 7 days. The Netdata team holds the final say when setting a disclosure date.

38 +

39 +[]()

docs/Performance.md

+2

@@ -231,3 +231,5 @@ Finally, if no web server is installed on your device, you can use port tcp/80 f

231 [web]

232 port = 80

233 ```

234 +

235 +[]()

docs/Running-behind-apache.md

+2

@@ -266,3 +266,5 @@ Make sure the requests reach netdata, by examing `/var/log/netdata/access.log`.

266

267 1. if the requests do not reach netdata, your apache does not forward them.

268 2. if the requests reach netdata by the URLs are wrong, you have not re-written them properly.

269 +

270 +[]()

docs/Running-behind-caddy.md

+2

@@ -25,3 +25,5 @@ netdata.domain.tld {

25 You would also need to instruct netdata to listen only to `127.0.0.1` or `::1`.

26

27 To limit access to netdata only from localhost, set `bind socket to IP = 127.0.0.1` or `bind socket to IP = ::1` in `/etc/netdata/netdata.conf`.

28 +

29 +[]()

docs/Running-behind-lighttpd.md

+2

@@ -58,3 +58,5 @@ enable web responses gzip compression = no

58 You would also need to instruct netdata to listen only to `127.0.0.1` or `::1`.

59

60 To limit access to netdata only from localhost, set `bind socket to IP = 127.0.0.1` or `bind socket to IP = ::1` in `/etc/netdata/netdata.conf`.

61 +

62 +[]()

docs/Running-behind-nginx.md

+2

@@ -200,3 +200,5 @@ If you get an 502 Bad Gateway error you might check your nginx error log:

200 ```

201

202 If you see something like the above, chances are high that SELinux prevents nginx from connecting to the backend server. To fix that, just use this policy: `setsebool -P httpd_can_network_connect true`.

203 +

204 +[]()

docs/Third-Party-Plugins.md

+2

@@ -27,3 +27,5 @@ Collect [number of currently logged-on users](https://github.com/veksh/netdata-n

27 ## Nim

28

29 There is an unofficial [nim plugin helper](https://github.com/FedericoCeratto/nim-netdata-plugin)

30 +

31 +[]()

docs/Why-Netdata.md

+2

@@ -168,3 +168,5 @@ Of course, there are a few issues that need to be addressed with this approach:

168 Our approach uses the netdata [registry](../registry/). The registry solves the problem of maintaining a list of all the netdata installations we have. It does this transparently, without any configuration. It tracks the netdata servers your web browser has visited and bookmarks them at the `my-netdata` menu.

169

170 Every netdata can be a registry. You can use the global one we provided for free, or pick one of your netdata servers and turn it to a registry for your network.

171 +

172 +[]()

docs/a-github-star-is-important.md

+2

@@ -11,3 +11,5 @@ So, give netdata a **GitHub star**, at the top right of this page.

11 Thank you!

12

13 Costa Tsaousis

14 +

15 +[]()

docs/configuration-guide.md

+2

@@ -114,3 +114,5 @@ Last, what about options you believe you have set, but you misspelled?When you g

114 Unix prefers regular expressions. But they are just too hard, too cryptic to use, write and understand.

115

116 So, netdata supports [simple patterns](../libnetdata/simple_pattern/).

117 +

118 +[]()

docs/generator/buildhtml.sh

+4 -1

@@ -24,7 +24,10 @@ cp -a ./${GENERATOR_DIR}/custom ./${GENERATOR_DIR}/src/

24

25 # Modify the first line of the main README.md, to enable proper static html generation

26 echo "Modifying README header"

27 -sed -i -e '0,/# netdata /s//# Introduction\n\n/' -e 's/\[!\[analytics.*UA-64295674-3)\]()//g' ${GENERATOR_DIR}/src/README.md

27 +sed -i -e '0,/# netdata /s//# Introduction\n\n/' ${GENERATOR_DIR}/src/README.md

28 +

29 +# Remove all GA tracking code

30 +find ${GENERATOR_DIR}/src -name "*.md" -print0 | xargs -0 sed -i -e 's/\[!\[analytics.*UA-64295674-3)\]()//g'

31

32 # Remove specific files that don't belong in the documentation

33 declare -a EXCLUDE_LIST=(

docs/high-performance-netdata.md

+2

@@ -147,3 +147,5 @@ Max open files 30000 30000 files

147 Max open files 30000 30000 files

148

149 ```

150 +

151 +[]()

docs/netdata-for-IoT.md

+2

@@ -37,3 +37,5 @@ sensors=force

37 Then restart netdata. You will get this:

38

39 

40 +

41 +[]()

docs/netdata-security.md

+2

@@ -167,3 +167,5 @@ path|owner|permissions| netdata |comments|

167 `/var/cache/netdata`|user&nbsp;`netdata`<br/>group&nbsp;`netdata`|dirs `0750`<br/>files `0660`|reads, writes, creates, deletes|**Netdata ephemeral database files**<br/>Netdata stores its ephemeral real-time database here.

168 `/var/lib/netdata`|user&nbsp;`netdata`<br/>group&nbsp;`netdata`|dirs `0750`<br/>files `0660`|reads, writes, creates, deletes|**Netdata permanent database files**<br/>Netdata stores here the registry data, health alarm log db, etc.

169 `/var/log/netdata`|user&nbsp;`netdata`<br/>group&nbsp;`root`|dirs `0755`<br/>files `0644`|writes, creates|**Netdata log files**<br/>all the Netdata applications, logs their errors or other informational messages to files in this directory. These files should be log rotated.

170 +

171 +[]()

docs/privacy-policy.md

+2

@@ -91,3 +91,5 @@ Data transferred from the European Union to the United States or outside the Eur

91 We may occasionally update this Privacy Policy. When we do, we will provide you with notice of such update through (at a minimum) a reasonably prominent notice on the Websites and Services, and will revise the Effective Date below. We encourage you to periodically review this Privacy Policy to stay informed about how we are protecting, using, processing and transferring the personal information we collect.

92

93 ***Effective Date: 10 November 2018.***

94 +

95 +[]()

docs/terms-of-use.md

+2

@@ -158,3 +158,5 @@ No agency relationship: The parties agree that no joint venture, partnership, em

158 Integration: These Master Terms and any applicable Additional Terms constitute the entire agreement between you and Netdata relating to this subject matter and supersede any and all prior communications and/or agreements between you and Netdata relating to access and use of the Services.

159

160 Human-readable summary of Sec 15: If there is a lawsuit arising from these terms, it should be in Delaware and governed by Delaware law. We are glad you use our sites, but this agreement does not mean we are partners.

161 +

162 +[]()

health/README.md

+2

@@ -653,3 +653,5 @@ You can find the context of charts by looking up the chart in either

653

654 You can find how netdata interpreted the expressions by examining the alarm at `http://your.netdata:19999/api/v1/alarms?all`. For each expression, netdata will return the expression as given in its config file, and the same expression with additional parentheses added to indicate the evaluation flow of the expression.

655

656 +

657 +[]()

health/notifications/README.md

+2 -1

@@ -62,4 +62,5 @@ If you need to dig even deeper, you can trace the execution with `bash -x`. Note

62 ```sh

63 bash -x /usr/libexec/netdata/plugins.d/alarm-notify.sh test

64 ```

65 - Then look in the output for the alarm-notify.sh calls and run the one you want to trace with `bash -x`.

\ No newline at end of file

65 + Then look in the output for the alarm-notify.sh calls and run the one you want to trace with `bash -x`.

66 +[]()

health/notifications/alerta/README.md

+2

@@ -78,3 +78,5 @@ you will not se them in main Alerta page, you need to select to see

78 that let us test each state one by one will be useful.

79

80 For more information see [https://docs.alerta.io](https://docs.alerta.io)

81 +

82 +[]()

health/notifications/awssns/README.md

+2

@@ -29,3 +29,5 @@ Notes:

29 * Netdata's native email notification support is far better in almost all respects than it's support through Amazon SNS. If you want email notifications, use the native support, not SNS.

30 * If you need to change the notification format for SNS notifications, you can do so by specifying the format in `AWSSNS_MESSAGE_FORMAT` in the configuration. This variable supports all the same vairiables you can use in custom notifications.

31 * While Amazon SNS supports sending differently formatted messages for different delivery methods, netdata does not currently support this functionality.

32 +

33 +[]()

health/notifications/discord/README.md

+2

@@ -42,3 +42,5 @@ role_recipients_discord[webmaster]="marketing development"

42 ```

43

44 The keywords `systems`, `databases`, `marketing`, `development` are discordapp.com channels (they should already exist within your discord server).

45 +

46 +[]()

health/notifications/email/README.md

+2

@@ -29,3 +29,5 @@ sudo su -s /bin/bash netdata

29 ```

30

31 Where `[ROLE]` is the role you want to test. The default (if you don't give a `[ROLE]`) is `sysadmin`.

32 +

33 +[]()

health/notifications/flock/README.md

+2

@@ -29,3 +29,5 @@ FLOCK_WEBHOOK_URL="https://api.flock.com/hooks/sendMessage/XXXXXXXXXXXXXXXXXXXXX

29 DEFAULT_RECIPIENT_FLOCK="alarms"

30

31 ```

32 +

33 +[]()

health/notifications/irc/README.md

+2

@@ -71,3 +71,5 @@ role_recipients_irc[webmaster]="#networking-alarms"

71 ```

72

73 The keywords `#user-alarms`, `#networking-alarms`, `#system-alarms`, `#databases-alarms` are irc channels which belong to the specified IRC network.

74 +

75 +[]()

health/notifications/kavenegar/README.md

+2

@@ -37,3 +37,5 @@ KAVENEGAR_API_KEY=""

37 KAVENEGAR_SENDER=""

38 DEFAULT_RECIPIENT_KAVENEGAR=""

39 ```

40 +

41 +[]()

health/notifications/messagebird/README.md

+2

@@ -37,3 +37,5 @@ MESSAGEBIRD_NUMBER="XXXXXXX"

37 DEFAULT_RECIPIENT_MESSAGEBIRD="XXXXXXX"

38

39 ```

40 +

41 +[]()

health/notifications/pagerduty/README.md

+2

@@ -33,3 +33,5 @@ SEND_PD="YES"

33 # (empty = do not send a notification for unconfigured roles):

34 DEFAULT_RECIPIENT_PD="<service key>"

35 ```

36 +

37 +[]()

health/notifications/pushbullet/README.md

+2

@@ -40,3 +40,5 @@ SEND_PUSHBULLET="YES"

40 PUSHBULLET_ACCESS_TOKEN="o.Sometokenhere"

41 DEFAULT_RECIPIENT_PUSHBULLET="admin1@example.com admin3@somemail.com"

42 ```

43 +

44 +[]()

health/notifications/pushover/README.md

+2

@@ -14,3 +14,5 @@ The configuration is like above (slack messages).

14 pushover.net notifications look like this:

15

16 

17 +

18 +[]()

health/notifications/rocketchat/README.md

+2

@@ -44,3 +44,5 @@ role_recipients_rocketchat[webmaster]="marketing development"

44

45 The keywords `systems`, `databases`, `marketing`, `development` are RocketChat channels (they should already exist).

46 Both public and private channels can be used, even if they differ from the channel configured in yout RocketChat incomming webhook.

47 +

48 +[]()

health/notifications/slack/README.md

+2

@@ -50,3 +50,5 @@ role_recipients_slack[sysadmin]="systems"

50 role_recipients_slack[dba]="databases systems"

51 role_recipients_slack[webmaster]="marketing development"

52 ```

53 +

54 +[]()

health/notifications/syslog/README.md

+2

@@ -21,3 +21,5 @@ Targets are defined as follows:

21 The `facility` and `level` are the standard syslog facility and level options, for more info on them see your local `logger` and `syslog` documentation. By default, netdata will log to the `local6` facility, with a log level dependent on the type of message (`crit` for CRITICAL, `warning` for WARNING, and `info` for everything else).

22

23 You can configure sending directly to remote log servers by specifying a host (and optionally a port). However, this has a somewhat high overhead, so it is much preferred to use your local syslog daemon to handle the forwarding of messages to remote systems (pretty much all of them allow at least simple forwarding, and most of the really popular ones support complex queueing and routing of messages to remote log servers).

24 +

25 +[]()

health/notifications/telegram/README.md

+2

@@ -17,3 +17,5 @@ See slack for configuration.

17 Telegram messages look like this:

18

19 

20 +

21 +[]()

health/notifications/twilio/README.md

+2

@@ -38,3 +38,5 @@ TWILIO_ACCOUNT_TOKEN="xxxxxxxxxx"

38 TWILIO_NUMBER="xxxxxxxxxxx"

39 DEFAULT_RECIPIENT_TWILIO="+15555555555"

40 ```

41 +

42 +[]()

health/notifications/web/README.md

+2

@@ -4,3 +4,5 @@ The netdata dashboard shows HTML notifications, when it is open.

4

5 Such web notifications look like this:

6 

7 +

8 +[]()

installer/README.md

+2

@@ -407,3 +407,5 @@ Additionally, as of 2018/06/24, the Netdata installer doesn't recognize DSM as a

407 # Netdata startup

408 [ -x /etc/rc.netdata ] && /etc/rc.netdata start

409 ```

410 +

411 +[]()

installer/UNINSTALL.md

+2

@@ -34,3 +34,5 @@ Delete the netdata files:

34 3. `userdel netdata`

35 4. `rm /etc/logrotate.d/netdata`

36 5. `rm /etc/systemd/system/netdata.service` or `rm /etc/init.d/netdata`, depending on the distro.

37 +

38 +[]()

installer/UPDATE.md

+2

@@ -69,3 +69,5 @@ If a newer version of netdata is not available from the source you got it, we su

69

70

71

72 +

73 +[]()

libnetdata/README.md

+2

@@ -4,3 +4,5 @@

4

5

6

7 +

8 +[]()

libnetdata/adaptive_resortable_list/README.md

+2

@@ -91,3 +91,5 @@ Compared to unoptimized code (test No 1: 4.6sec):

91

92 Do not use ARL if the a name/keyword may appear more than once in the

93 source data.

94 +

95 +[]()

libnetdata/avl/README.md

+2 -1

@@ -8,4 +8,5 @@ use any memory allocations and their memory footprint is optimized

8 (by eliminating non-necessary data members).

9

10 In addition to the above, this version of AVL, provides versions using locks

11 -and traversal functions.

\ No newline at end of file

11 +and traversal functions.

12 +[]()

libnetdata/buffer/README.md

+2 -1

@@ -8,4 +8,5 @@ Also, they are super fast in printing and appending data to the string and its `

8 is just a lookup (it does not traverse the string).

9

10 Netdata uses `BUFFER`s for preparing web responses and buffering data to be sent upstream or

11 -to backend databases.

\ No newline at end of file

11 +to backend databases.

12 +[]()

libnetdata/clocks/README.md

+2

@@ -0,0 +1,2 @@

1 +

2 +[]()

libnetdata/config/README.md

+2

@@ -44,3 +44,5 @@ Last, what about options you believe you have set, but you misspelled?

44 When you get the configuration file from the server, there will be a

45 comment above all `name = value` pairs the server does not use.

46 So you know that whatever you wrote there, is not used.

47 +

48 +[]()

libnetdata/dictionary/README.md

+2

@@ -0,0 +1,2 @@

1 +

2 +[]()

libnetdata/eval/README.md

+2

@@ -0,0 +1,2 @@

1 +

2 +[]()

libnetdata/locks/README.md

+2

@@ -0,0 +1,2 @@

1 +

2 +[]()

libnetdata/log/README.md

+2

@@ -0,0 +1,2 @@

1 +

2 +[]()

libnetdata/popen/README.md

+2

@@ -0,0 +1,2 @@

1 +

2 +[]()

libnetdata/procfile/README.md

+2

@@ -59,3 +59,5 @@ To achieve this kind of performance, the library tries to work in batches so tha

59 and the data are inside the processor's caches.

60

61 This library is extensively used in netdata and its plugins.

62 +

63 +[]()

libnetdata/simple_pattern/README.md

+2

@@ -34,3 +34,5 @@ netdata stops processing to the first positive or negative match

34 (left to right). If it is not matched by either positive or negative

35 patterns, it is denied at the end.

36

37 +

38 +[]()

libnetdata/socket/README.md

+2

@@ -0,0 +1,2 @@

1 +

2 +[]()

libnetdata/statistical/README.md

+2

@@ -0,0 +1,2 @@

1 +

2 +[]()

libnetdata/storage_number/README.md

+2

@@ -8,3 +8,5 @@ with a precision of 0.00001 (yes, it's a floating point number, meaning that hig

8 have less decimal precision) and 3 bits for flags.

9

10 This provides an extremely optimized memory footprint with just 0.0001% max accuracy loss.

11 +

12 +[]()

libnetdata/threads/README.md

+2

@@ -0,0 +1,2 @@

1 +

2 +[]()

libnetdata/url/README.md

+2

@@ -0,0 +1,2 @@

1 +

2 +[]()

makeself/README.md

+2

@@ -44,3 +44,5 @@ If netdata crashes, `valgrind` will print a stack trace of the issue. Open a git

44 To stop netdata while it runs under `valgrind`, press Control-C on the console.

45

46 > If you omit the parameter `--undef-value-errors=no` to valgrind, you will get hundreds of errors about conditional jumps that depend on uninitialized values. This is normal. Valgrind has heuristics to prevent it from printing such errors for system libraries, but for the static netdata binary, all the required libraries are built into netdata. So, valgrind cannot appply its heuristics and prints them.

47 +

48 +[]()

packaging/docker/README.md

+2

@@ -116,3 +116,5 @@ services:

116 ### Restrict access with basic auth

117

118 You can restrict access by following [official caddy guide](https://caddyserver.com/docs/basicauth) and adding lines to Caddyfile.

119 +

120 +[]()

packaging/maintainers/README.md

+2

@@ -71,3 +71,5 @@ MacOS Homebrew Formula|[link](https://github.com/Homebrew/homebrew-core/blob/mas

71 ## Packages summary from repology.org

72

73 [](https://repology.org/metapackage/netdata/versions)

74 +

75 +[]()

registry/README.md

+2

@@ -150,3 +150,5 @@ ERROR 409: Cannot ACCESS netdata registry: https://registry.my-netdata.io respon

150 ```

151

152 This error is printed on your web browser console (press F12 on your browser to see it).

153 +

154 +[]()

streaming/README.md

+2

@@ -413,3 +413,5 @@ The sending side of a netdata proxy, connects and disconnects to the final desti

413 metrics, following the same pattern of the receiving side.

414

415 For a practical example see [Monitoring ephemeral nodes](#monitoring-ephemeral-nodes).

416 +

417 +[]()

tests/README.md

+3

@@ -134,3 +134,6 @@ Apparently, jasmine-node can produce a junit report with the `--junitreport` fla

134 The karma and node.d runners can be integrated in Travis (AFAIK), but that is outside my ability.

135

136 Note: Karma is for browser-testing. On a build server, no GUI or browser might by available, unless browsers support headless mode.

137 +

138 +

139 +[]()

web/README.md

+2

@@ -24,3 +24,5 @@ To configure your info file set in netdata.conf:

24 [web]

25 custom dashboard_info.js = your_file_name.js

26 ```

27 +

28 +[]()

web/api/README.md

+2

@@ -17,3 +17,5 @@ Check this [single chart, jsfiddle example](https://jsfiddle.net/ktsaou/ensu4uws

17 and this [multi chart, jsfiddle example](https://jsfiddle.net/ktsaou/L5y2eqp2/):

18

19 

20 +

21 +[]()

web/api/badges/README.md

+2

@@ -304,3 +304,5 @@ You can refresh them from your browser console though. Press F12 to open the web

304 ```js

305 var len = document.images.length; while(len--) { document.images[len].src = document.images[len].src.replace(/\?cacheBuster=\d*/, "") + "?cacheBuster=" + new Date().getTime().toString(); };

306 ```

307 +

308 +[]()

web/api/exporters/README.md

+2

@@ -1,3 +1,5 @@

1 # Exporters

2

3 TBD

4 +

5 +[]()

web/api/exporters/prometheus/README.md

+2

@@ -1,3 +1,5 @@

1 # prometheus exporter

2

3 The prometheus exporter for netdata is located at the [backends section for prometheus](../../../../backends/prometheus).

4 +

5 +[]()

web/api/exporters/shell/README.md

+2

@@ -62,3 +62,5 @@ NETDATA_${chart_id^^}_${dimension_id^^}="${value}"

62 ```

63

64 The value is rounded to the closest integer, since shell script cannot process decimal numbers.

65 +

66 +[]()

web/api/formatters/README.md

+2

@@ -70,3 +70,5 @@ For example, to download a CSV file with CPU utilization of the last hour,

70

71 This is done by appending `&tqx=outFileName:FILENAME` to any data query.

72 The output will be in the format given with `&format=`.

73 +

74 +[]()

web/api/formatters/csv/README.md

+2

@@ -137,3 +137,5 @@ time|started

137 2018-10-27 03:45:00|205.001551

138 2018-10-27 03:44:00|7026.9852167

139 2018-10-27 03:43:00|205.9904794

140 +

141 +[]()

web/api/formatters/json/README.md

+2

@@ -148,3 +148,5 @@ google.visualization.Query.setResponse({version:'0.6',reqId:'0',status:'ok',sig:

148 }});

149 ```

150

151 +

152 +[]()

web/api/formatters/ssv/README.md

+2

@@ -50,3 +50,5 @@ in a JSON array:

50 # curl -Ss 'https://registry.my-netdata.io/api/v1/data?chart=nginx_local.connections&format=array&after=-3600&points=12&group=max'

51 [278,258,268,239,259,260,243,266,278,318,264,258]

52 ```

53 +

54 +[]()

web/api/formatters/value/README.md

+2

@@ -15,3 +15,5 @@ option|supported|description

15 The Value formatter is not exposed by the API by itself.

16 Instead it is used by the [`ssv`](../ssv) formatter

17 and [health monitoring queries](../../../../health).

18 +

19 +[]()

web/api/health/README.md

+2

@@ -40,3 +40,5 @@ The following will return an SVG badge of the alarm named `NAME`, attached to th

40

41 `http://your.netdata.ip:19999/api/v1/badge.svg?alarm=NAME&chart=CHART`

42

43 +

44 +[]()

web/api/queries/README.md

+2

@@ -168,3 +168,5 @@ So, the proper way to query the database is to also set at least `after`. The fo

168 http://netdata.firehol.org/api/v1/data?chart=system.cpu&points=1&after=-10&options=seconds

169

170 When you keep calling this URL, you will see that it returns one new value every 10 seconds, and the timestamp always ends with zero. Similarly, if you say `points=1&after=-5` it will always return timestamps ending with 0 or 5.

171 +

172 +[]()

web/api/queries/average/README.md

+2

@@ -37,3 +37,5 @@ Examining last 1 minute `successful` web server responses:

37 ## References

38

39 - [https://en.wikipedia.org/wiki/Average](https://en.wikipedia.org/wiki/Average).

40 +

41 +[]()

web/api/queries/des/README.md

+2

@@ -64,3 +64,5 @@ Examining last 1 minute `successful` web server responses:

64 ## References

65

66 - [https://en.wikipedia.org/wiki/Exponential_smoothing](https://en.wikipedia.org/wiki/Exponential_smoothing).

67 +

68 +[]()

web/api/queries/incremental_sum/README.md

+2

@@ -32,3 +32,5 @@ Examining last 1 minute `successful` web server responses:

32 ## References

33

34 - none

35 +

36 +[]()

web/api/queries/max/README.md

+2

@@ -29,3 +29,5 @@ Examining last 1 minute `successful` web server responses:

29 ## References

30

31 - [https://en.wikipedia.org/wiki/Sample_maximum_and_minimum](https://en.wikipedia.org/wiki/Sample_maximum_and_minimum).

32 +

33 +[]()

web/api/queries/median/README.md

+2

@@ -35,3 +35,5 @@ Examining last 1 minute `successful` web server responses:

35 ## References

36

37 - [https://en.wikipedia.org/wiki/Median](https://en.wikipedia.org/wiki/Median).

38 +

39 +[]()

web/api/queries/min/README.md

+2

@@ -29,3 +29,5 @@ Examining last 1 minute `successful` web server responses:

29 ## References

30

31 - [https://en.wikipedia.org/wiki/Sample_maximum_and_minimum](https://en.wikipedia.org/wiki/Sample_maximum_and_minimum).

32 +

33 +[]()

web/api/queries/ses/README.md

+2

@@ -52,3 +52,5 @@ Examining last 1 minute `successful` web server responses:

52

53 - [https://en.wikipedia.org/wiki/Moving_average#exponential-moving-average](https://en.wikipedia.org/wiki/Moving_average#exponential-moving-average)

54 - [https://en.wikipedia.org/wiki/Exponential_smoothing](https://en.wikipedia.org/wiki/Exponential_smoothing).

55 +

56 +[]()

web/api/queries/stddev/README.md

+2

@@ -85,3 +85,5 @@ Examining last 1 minute `successful` web server responses:

85 ## References

86

87 Check [https://en.wikipedia.org/wiki/Coefficient_of_variation](https://en.wikipedia.org/wiki/Coefficient_of_variation).

88 +

89 +[]()

web/api/queries/sum/README.md

+2

@@ -32,3 +32,5 @@ Examining last 1 minute `successful` web server responses:

32 ## References

33

34 - [https://en.wikipedia.org/wiki/Summation](https://en.wikipedia.org/wiki/Summation).

35 +

36 +[]()

web/gui/README.md

+2

@@ -104,3 +104,5 @@ This is a chart that displays the hotwater temperature in the given range of 40

104 ></div>

105 ```

106 

107 +

108 +[]()

web/gui/confluence/README.md

+2

@@ -1010,3 +1010,5 @@ NETDATA.options.current.eliminate_zero_dimensions = false;

1010 </span>

1011 </div>

1012 ```

1013 +

1014 +[]()

web/gui/custom/README.md

+2

@@ -410,3 +410,5 @@ Charts can be scaled to specific units with `data-desired-units="UNITS"`. If the

410 ></div>

411 ```

412

413 +

414 +[]()

web/server/README.md

+2

@@ -120,3 +120,5 @@ If you publish your netdata to the internet, you may want to apply some protecti

120 4. Run netdata with a low process scheduling priority (the default is the lowest)

121 5. If possible, proxy netdata via a full featured web server (nginx, apache, etc)

122

123 +

124 +[]()

web/server/multi/README.md

+2 -1

@@ -5,4 +5,5 @@ The `multi-threaded` web server spawns a thread for each connection it receives.

5 Each thread uses non-blocking I/O so it can serve any number of web requests in parallel,

6 though this is not supported by HTTP, so in practice each thread serves all the requests sequentially.

7

8 -Each thread respects the `keep-alive` HTTP header to serve multiple HTTP requests via the same connection.

\ No newline at end of file

8 +Each thread respects the `keep-alive` HTTP header to serve multiple HTTP requests via the same connection.

9 +[]()

web/server/single/README.md

+2 -1

@@ -3,4 +3,5 @@

3 The `single-threaded` web server runs as a single thread inside netdata.

4 It uses non-blocking I/O so it can serve any number of web requests in parallel.

5

6 -This web server respects the `keep-alive` HTTP header to serve multiple HTTP requests via the same connection.

\ No newline at end of file

6 +This web server respects the `keep-alive` HTTP header to serve multiple HTTP requests via the same connection.

7 +[]()

web/server/static/README.md

+2 -1

@@ -6,4 +6,5 @@ The kernel distributes the incoming requests to them.

6

7 Each thread uses non-blocking I/O so it can serve any number of web requests in parallel.

8

9 -This web server respects the `keep-alive` HTTP header to serve multiple HTTP requests via the same connection.

\ No newline at end of file

9 +This web server respects the `keep-alive` HTTP header to serve multiple HTTP requests via the same connection.

10 +[]()