Docs: Removed Google Analytics tags (#12145)
Tina Luedtke committed
Feb 17, 2022 at 10:37 UTC
c7f2647a62f73b5bfec7545c019b11efadbca2bb
316 files changed
+294
-327
BREAKING_CHANGES.md
+1
-1
@@ -8,4 +8,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/BREAKING_CHANGES
8
9
- remove deprecated bash modules (`apache`, `cpu_apps`, `cpufreq`, `exim`, `hddtemp`, `load_average`, `mem_apps`, `mysql`, `nginx`, `phpfpm`, `postfix`, `squid`, `tomcat`) [[#7962](https://github.com/netdata/netdata/pull/7962)]
10
11
-[](<>)
11
+
BUILD.md
+1
-1
@@ -362,4 +362,4 @@ Some smaller miscellaneous suggestions:
362
* [header checks in CMake](https://stackoverflow.com/questions/647892/how-to-check-header-files-and-library-functions-in-cmake-like-it-is-done-in-auto)
363
* [how to write platform checks](https://gitlab.kitware.com/cmake/community/wikis/doc/tutorials/How-To-Write-Platform-Checks)
364
365
-[](<>)
365
+
README.md
-1
@@ -8,7 +8,6 @@
8
<a href="https://travis-ci.com/netdata/netdata"><img src="https://travis-ci.com/netdata/netdata.svg?branch=master" alt="Build status"></a>
9
<a href="https://bestpractices.coreinfrastructure.org/projects/2231"><img src="https://bestpractices.coreinfrastructure.org/projects/2231/badge" alt="CII Best Practices"></a>
10
<a href="https://www.gnu.org/licenses/gpl-3.0"><img src="https://img.shields.io/badge/License-GPL%20v3%2B-blue.svg" alt="License: GPL v3+"></a>
11
- <a href="<>"><img src="https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Freadme&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3" alt="analytics"></a>
11
<br />
12
<a href="https://codeclimate.com/github/netdata/netdata"><img src="https://codeclimate.com/github/netdata/netdata/badges/gpa.svg" alt="Code Climate"></a>
13
<a href="https://www.codacy.com/app/netdata/netdata?utm_source=github.com&utm_medium=referral&utm_content=netdata/netdata&utm_campaign=Badge_Grade"><img src="https://api.codacy.com/project/badge/Grade/a994873f30d045b9b4b83606c3eb3498" alt="Codacy"></a>
REDISTRIBUTED.md
+1
-1
@@ -180,4 +180,4 @@ connectivity is not available.
180
181
Copyright 2015, Benedikt Schmitt [Unlicense License](https://unlicense.org/)
182
183
-[](<>)
183
+
aclk/README.md
+1
-1
@@ -134,4 +134,4 @@ If you changed the runtime setting in your `var/lib/netdata/cloud.d/cloud.conf`
134
135
Restart your Agent and [connect your node](/claim/README.md#how-to-connect-a-node).
136
137
-[](<>)
137
+
backends/README.md
+1
-1
@@ -233,4 +233,4 @@ Netdata adds 4 alarms:
233
234
235
236
-[](<>)
236
+
backends/TIMESCALE.md
+1
-1
@@ -54,4 +54,4 @@ blog](https://blog.timescale.com/blog/writing-it-metrics-from-netdata-to-timesca
54
Thank you to Mahlon, Rune, TimescaleDB, and the members of the Netdata community that requested and then built this
55
backend connection between Netdata and TimescaleDB!
56
57
-[](<>)
57
+
backends/WALKTHROUGH.md
+1
-1
@@ -255,4 +255,4 @@ achieved you do not have to think about the monitoring system until Prometheus c
255
happens there are options presented in the Prometheus documentation for solving this. Hope this was helpful, happy
256
monitoring.
257
258
-[](<>)
258
+
backends/aws_kinesis/README.md
+1
-1
@@ -50,4 +50,4 @@ Alternatively, AWS credentials can be set for the `netdata` user using AWS SDK f
50
A partition key for every record is computed automatically by Netdata with the purpose to distribute records across
51
available shards evenly.
52
53
-[](<>)
53
+
backends/mongodb/README.md
+1
-1
@@ -38,4 +38,4 @@ collection = your_collection_name
38
The default socket timeout depends on the backend update interval. The timeout is 500 ms shorter than the interval (but
39
not less than 1000 ms). You can alter the timeout using the `sockettimeoutms` MongoDB URI option.
40
41
-[](<>)
41
+
backends/opentsdb/README.md
-1
@@ -35,4 +35,3 @@ After your proxy is configured, make the following changes to `netdata.conf`:
35
In this example, we used the port `8082` for our reverse proxy. If your reverse proxy listens on a different port,
36
change the `destination = localhost:8082` line accordingly.
37
38
-[]()
backends/prometheus/README.md
+1
-1
@@ -454,4 +454,4 @@ through a web proxy, or when multiple prometheus servers are NATed to a single I
454
`&server=NAME` to the URL. This `NAME` is used by Netdata to uniquely identify each prometheus server and keep track of
455
its last access time.
456
457
-[](<>)
457
+
backends/prometheus/remote_write/README.md
+1
-1
@@ -38,4 +38,4 @@ buffer size on failures.
38
39
The remote write backend does not support `buffer on failures`
40
41
-[](<>)
41
+
build_external/README.md
+1
-1
@@ -125,4 +125,4 @@ Notes:
125
* There is not yet a good way to configure the target agent container from the docker-compose command line.
126
* Several other containers should be in this compose (a paho client, tshark etc).
127
128
-[]()
128
+
claim/README.md
+1
-1
@@ -548,4 +548,4 @@ Rooms you added that node to.
548
The user can also put the Cloud endpoint's full certificate chain in `cloud.d/cloud_fullchain.pem` so that the Agent
549
can trust the endpoint if necessary.
550
551
-[](<>)
551
+
cli/README.md
+1
-1
@@ -37,4 +37,4 @@ aclk-state [json]
37
38
Those commands are the same that can be sent to netdata via [signals](/daemon/README.md#command-line-options).
39
40
-[](<>)
40
+
collectors/COLLECTORS.md
+1
-1
@@ -540,4 +540,4 @@ default. To use a third-party collector, visit their GitHub/documentation page a
540
- [charts.d example](charts.d.plugin/example/README.md): An example `charts.d` collector.
541
- [python.d example](python.d.plugin/example/README.md): An example `python.d` collector.
542
543
-[](<>)
543
+
collectors/README.md
+1
-1
@@ -46,4 +46,4 @@ long-term metrics storage, by archiving metrics to like Graphite, Prometheus, Mo
46
**[Exporting](/exporting/README.md)**: An experimental refactoring of our backends system with a modular system and
47
support for exporting metrics to multiple systems simultaneously.
48
49
-[](<>)
49
+
collectors/REFERENCE.md
-1
@@ -179,4 +179,3 @@ through this, is to examine what other similar plugins do.
179
180
You can add custom collectors by following the [external plugins documentation](/collectors/plugins.d/README.md).
181
182
-[]()
collectors/apps.plugin/README.md
+1
-1
@@ -396,4 +396,4 @@ if you sum the CPU utilization of all processes, you might have more CPU time th
396
total cpu time of the system. Netdata solves this, by adapting the per process cpu utilization to
397
the total of the system. [Netdata adds charts that document this normalization](https://london.my-netdata.io/default.html#menu_netdata_submenu_apps_plugin).
398
399
-[](<>)
399
+
collectors/cgroups.plugin/README.md
+1
-1
@@ -284,4 +284,4 @@ So, when a network interface or container stops, Netdata might log a few errors
284
285
Network interfaces are monitored by means of the [proc plugin](/collectors/proc.plugin/README.md#monitored-network-interface-metrics).
286
287
-[](<>)
287
+
collectors/charts.d.plugin/README.md
+1
-1
@@ -195,4 +195,4 @@ This is what you need to do:
195
Execute the above in this order, since Netdata will (by default) attempt to start new plugins soon after they are
196
created in `/usr/libexec/netdata/plugins.d/`.
197
198
-[](<>)
198
+
collectors/charts.d.plugin/ap/README.md
+1
-1
@@ -96,4 +96,4 @@ You can only set `ap_update_every=NUMBER` to change the data collection frequenc
96
97
The plugin is able to auto-detect if you are running access points on your linux box.
98
99
-[](<>)
99
+
collectors/charts.d.plugin/apcupsd/README.md
+1
-1
@@ -18,4 +18,4 @@ cd /etc/netdata # Replace this path with your Netdata config directory, if dif
18
sudo ./edit-config charts.d/apcupsd.conf
19
```
20
21
-[](<>)
21
+
collectors/charts.d.plugin/example/README.md
+1
-1
@@ -7,4 +7,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/chart
7
8
If you want to understand how charts.d data collector functions, check out the [charts.d example](https://raw.githubusercontent.com/netdata/netdata/master/collectors/charts.d.plugin/example/example.chart.sh).
9
10
-[](<>)
10
+
collectors/charts.d.plugin/libreswan/README.md
+1
-1
@@ -53,4 +53,4 @@ Make sure the path `/sbin/ipsec` matches your setup (execute `which ipsec` to fi
53
54
---
55
56
-[](<>)
56
+
collectors/charts.d.plugin/nut/README.md
+1
-1
@@ -71,4 +71,4 @@ nut_update_every=2
71
72
---
73
74
-[](<>)
74
+
collectors/charts.d.plugin/opensips/README.md
+1
-1
@@ -16,4 +16,4 @@ cd /etc/netdata # Replace this path with your Netdata config directory, if dif
16
sudo ./edit-config charts.d/opensips.conf
17
```
18
19
-[](<>)
19
+
collectors/charts.d.plugin/sensors/README.md
+1
-1
@@ -81,4 +81,4 @@ sensors_excluded=()
81
82
---
83
84
-[](<>)
84
+
collectors/checks.plugin/README.md
+1
-1
@@ -7,4 +7,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/check
7
8
A debugging plugin (by default it is disabled)
9
10
-[](<>)
10
+
collectors/cups.plugin/README.md
+1
-1
@@ -59,4 +59,4 @@ For each destination the plugin provides these charts:
59
60
At the moment only job status pending, processing, and held are reported because we do not have a method to collect stopped, canceled, aborted and completed jobs which scales.
61
62
-[]()
62
+
collectors/diskspace.plugin/README.md
+1
-1
@@ -40,4 +40,4 @@ Charts can be enabled/disabled for every mount separately:
40
41
> for disks performance monitoring, see the `proc` plugin, [here](/collectors/proc.plugin/README.md#monitoring-disks)
42
43
-[](<>)
43
+
collectors/ebpf.plugin/README.md
+1
-1
@@ -899,4 +899,4 @@ shows how the lockdown module impacts `ebpf.plugin` based on the selected option
899
If you or your distribution compiled the kernel with the last combination, your system cannot load shared libraries
900
required to run `ebpf.plugin`.
901
902
-[](<>)
902
+
collectors/fping.plugin/README.md
+1
-1
@@ -99,4 +99,4 @@ That's it. Netdata will detect the new plugin and start it.
99
You can name the new plugin any name you like.
100
Just make sure the plugin and the configuration file have the same name.
101
102
-[](<>)
102
+
collectors/freebsd.plugin/README.md
+1
-1
@@ -9,4 +9,4 @@ Collects resource usage and performance data on FreeBSD systems
9
10
By default, Netdata will enable monitoring metrics for disks, memory, and network only when they are not zero. If they are constantly zero they are ignored. Metrics that will start having values, after Netdata is started, will be detected and charts will be automatically added to the dashboard (a refresh of the dashboard is needed for them to appear though). Use `yes` instead of `auto` in plugin configuration sections to enable these charts permanently. You can also set the `enable zero metrics` option to `yes` in the `[global]` section which enables charts with zero metrics for all internal Netdata plugins.
11
12
-[](<>)
12
+
collectors/freeipmi.plugin/README.md
+1
-1
@@ -191,4 +191,4 @@ If you need to disable IPMI for Netdata, edit `/etc/netdata/netdata.conf` and se
191
freeipmi = no
192
```
193
194
-[](<>)
194
+
collectors/idlejitter.plugin/README.md
+1
-1
@@ -29,4 +29,4 @@ idlejitter.plugin generates the idlejitter chart which measures CPU idle jitter
29
30
This chart is available without any configuration.
31
32
-[](<>)
32
+
collectors/ioping.plugin/README.md
+1
-1
@@ -83,4 +83,4 @@ That's it. Netdata will detect the new plugin and start it.
83
You can name the new plugin any name you like.
84
Just make sure the plugin and the configuration file have the same name.
85
86
-[](<>)
86
+
collectors/macos.plugin/README.md
+1
-1
@@ -9,4 +9,4 @@ Collects resource usage and performance data on macOS systems
9
10
By default, Netdata will enable monitoring metrics for disks, memory, and network only when they are not zero. If they are constantly zero they are ignored. Metrics that will start having values, after Netdata is started, will be detected and charts will be automatically added to the dashboard (a refresh of the dashboard is needed for them to appear though). Use `yes` instead of `auto` in plugin configuration sections to enable these charts permanently. You can also set the `enable zero metrics` option to `yes` in the `[global]` section which enables charts with zero metrics for all internal Netdata plugins.
11
12
-[](<>)
12
+
collectors/nfacct.plugin/README.md
+1
-1
@@ -51,4 +51,4 @@ sudo /usr/libexec/netdata/plugins.d/nfacct.plugin 1 debug
51
52
You will get verbose output on what the plugin does.
53
54
-[](<>)
54
+
collectors/node.d.plugin/README.md
+1
-1
@@ -233,4 +233,4 @@ The `service` object defines a set of functions to allow you send information to
233
_FIXME: document an operational node.d.plugin data collector - the best example is the
234
[snmp collector](https://raw.githubusercontent.com/netdata/netdata/master/collectors/node.d.plugin/snmp/snmp.node.js)_
235
236
-[](<>)
236
+
collectors/node.d.plugin/fronius/README.md
+1
-1
@@ -132,4 +132,4 @@ The output of /solar_api/v1/GetPowerFlowRealtimeData.fcgi looks like this:
132
}
133
```
134
135
-[](<>)
135
+
collectors/node.d.plugin/named/README.md
+1
-1
@@ -345,4 +345,4 @@ Verify it works by running the following command (the collector is written in no
345
curl "http://localhost:8888/json/v1/server"
346
```
347
348
-[](<>)
348
+
collectors/node.d.plugin/sma_webbox/README.md
+1
-1
@@ -30,4 +30,4 @@ The module supports any number of name servers:
30
}
31
```
32
33
-[](<>)
33
+
collectors/node.d.plugin/snmp/README.md
+1
-1
@@ -442,4 +442,4 @@ This switch has a very slow SNMP processors. To respond, it needs about 8 second
442
}
443
```
444
445
-[](<>)
445
+
collectors/node.d.plugin/stiebeleltron/README.md
+1
-1
@@ -522,4 +522,4 @@ The charts are being generated using the configuration below. So if your install
522
}
523
```
524
525
-[](<>)
525
+
collectors/perf.plugin/README.md
+1
-1
@@ -77,4 +77,4 @@ sudo /usr/libexec/netdata/plugins.d/perf.plugin 1 all debug
77
78
You will get verbose output on what the plugin does.
79
80
-[](<>)
80
+
collectors/plugins.d/README.md
+1
-1
@@ -481,4 +481,4 @@ There are a few rules for writing plugins properly:
481
482
4. If possible, try to autodetect if your plugin should be enabled, without any configuration.
483
484
-[](<>)
484
+
collectors/proc.plugin/README.md
+1
-1
@@ -604,4 +604,4 @@ As far as the message queue charts are dynamic, sane limits are applied for the
604
# max dimensions in memory allowed = 50
605
```
606
607
-[](<>)
607
+
collectors/python.d.plugin/README.md
+1
-1
@@ -270,4 +270,4 @@ At minimum, to be buildable and testable, the PR needs to include:
270
- Optionally, chart information in `web/gui/dashboard_info.js`. This generally involves specifying a name and icon for the section, and may include descriptions for the section or individual charts.
271
- Optionally, some default alarm configurations for your collector in `health/health.d/<module_name>.conf` and a line adding `<module_name>.conf` in `health/Makefile.am`.
272
273
-[](<>)
273
+
collectors/python.d.plugin/adaptec_raid/README.md
+1
-1
@@ -77,4 +77,4 @@ sudo ./edit-config python.d/adaptec_raid.conf
77
78
---
79
80
-[](<>)
80
+
collectors/python.d.plugin/alarms/README.md
-2
@@ -56,5 +56,3 @@ local:
56
```
57
58
It will default to pulling all alarms at each time step from the Netdata rest api at `http://127.0.0.1:19999/api/v1/alarms?all`
59
-
60
-[]()
collectors/python.d.plugin/am2320/README.md
-1
@@ -51,4 +51,3 @@ Software install:
51
- restart the netdata service.
52
- check the dashboard.
53
54
-[]()
collectors/python.d.plugin/anomalies/README.md
-1
@@ -241,4 +241,3 @@ If you would like to go deeper on what exactly the anomalies collector is doing
241
- Good [blog post](https://www.anodot.com/blog/what-is-anomaly-detection/) from Anodot on time series anomaly detection. Anodot also have some great whitepapers in this space too that some may find useful.
242
- Novelty and outlier detection in the [scikit-learn documentation](https://scikit-learn.org/stable/modules/outlier_detection.html).
243
244
-[]()
collectors/python.d.plugin/apache/README.md
+1
-1
@@ -79,4 +79,4 @@ Without configuration, module attempts to connect to `http://localhost/server-st
79
80
---
81
82
-[](<>)
82
+
collectors/python.d.plugin/beanstalk/README.md
+1
-1
@@ -130,4 +130,4 @@ If no configuration is given, module will attempt to connect to beanstalkd on `1
130
131
---
132
133
-[](<>)
133
+
collectors/python.d.plugin/bind_rndc/README.md
+1
-1
@@ -76,4 +76,4 @@ If no configuration is given, module will attempt to read named.stats file at `
76
77
---
78
79
-[](<>)
79
+
collectors/python.d.plugin/boinc/README.md
+1
-1
@@ -38,4 +38,4 @@ remote:
38
39
---
40
41
-[](<>)
41
+
collectors/python.d.plugin/ceph/README.md
+1
-1
@@ -45,4 +45,4 @@ local:
45
46
---
47
48
-[](<>)
48
+
collectors/python.d.plugin/changefinder/README.md
-1
@@ -215,4 +215,3 @@ sudo su -s /bin/bash netdata
215
- Novelty and outlier detection in
216
the [scikit-learn documentation](https://scikit-learn.org/stable/modules/outlier_detection.html).
217
218
-[]()
collectors/python.d.plugin/chrony/README.md
+1
-1
@@ -58,4 +58,4 @@ local:
58
Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate
59
method](/docs/configure/start-stop-restart.md) for your system, to finish configuring the `chrony` collector.
60
61
-[](<>)
61
+
collectors/python.d.plugin/couchdb/README.md
+1
-1
@@ -50,4 +50,4 @@ local:
50
51
---
52
53
-[](<>)
53
+
collectors/python.d.plugin/dns_query_time/README.md
+1
-1
@@ -26,4 +26,4 @@ sudo ./edit-config python.d/dns_query_time.conf
26
27
---
28
29
-[](<>)
29
+
collectors/python.d.plugin/dnsdist/README.md
+1
-1
@@ -69,4 +69,4 @@ localhost:
69
X-API-Key: 'dnsdist-api-key'
70
```
71
72
-[](<>)
72
+
collectors/python.d.plugin/dockerd/README.md
+1
-1
@@ -43,4 +43,4 @@ sudo ./edit-config python.d/dockerd.conf
43
44
---
45
46
-[](<>)
46
+
collectors/python.d.plugin/dovecot/README.md
+1
-1
@@ -102,4 +102,4 @@ If no configuration is given, module will attempt to connect to dovecot using un
102
103
---
104
105
-[](<>)
105
+
collectors/python.d.plugin/elasticsearch/README.md
+1
-1
@@ -91,4 +91,4 @@ If no configuration is given, module will try to connect to `http://127.0.0.1:92
91
92
---
93
94
-[](<>)
94
+
collectors/python.d.plugin/energid/README.md
+1
-1
@@ -74,4 +74,4 @@ bitcoin:
74
75
---
76
77
-[](<>)
77
+
collectors/python.d.plugin/example/README.md
+1
-1
@@ -11,4 +11,4 @@ Netdata provides an [example python data collection module](https://github.com/n
11
12
If you want to write your own collector, read our [writing a new Python module](/collectors/python.d.plugin/README.md#how-to-write-a-new-module) tutorial.
13
14
-[](<>)
14
+
collectors/python.d.plugin/exim/README.md
+1
-1
@@ -38,4 +38,4 @@ Configuration is not needed.
38
39
---
40
41
-[](<>)
41
+
collectors/python.d.plugin/fail2ban/README.md
+1
-1
@@ -79,4 +79,4 @@ at `/etc/fail2ban/jail.local`. If conf file is not found default jail is `ssh`.
79
80
---
81
82
-[](<>)
82
+
collectors/python.d.plugin/freeradius/README.md
+1
-1
@@ -87,4 +87,4 @@ and restart/reload your FREERADIUS server.
87
88
---
89
90
-[](<>)
90
+
collectors/python.d.plugin/gearman/README.md
-1
@@ -48,4 +48,3 @@ localhost:
48
49
When no configuration file is found, module tries to connect to TCP/IP socket: `localhost:4730`.
50
51
-[]()
collectors/python.d.plugin/go_expvar/README.md
+1
-1
@@ -316,4 +316,4 @@ The images below show how do the final charts in Netdata look.
316
317
318
319
-[](<>)
319
+
collectors/python.d.plugin/haproxy/README.md
+1
-1
@@ -64,4 +64,4 @@ If no configuration is given, module will fail to run.
64
65
---
66
67
-[](<>)
67
+
collectors/python.d.plugin/hddtemp/README.md
+1
-1
@@ -35,4 +35,4 @@ If no configuration is given, module will attempt to connect to hddtemp daemon o
35
36
---
37
38
-[](<>)
38
+
collectors/python.d.plugin/hpssa/README.md
-1
@@ -81,4 +81,3 @@ ssacli_path: /usr/sbin/ssacli
81
Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate
82
method](/docs/configure/start-stop-restart.md) for your system.
83
84
-[]()
collectors/python.d.plugin/httpcheck/README.md
+1
-1
@@ -56,4 +56,4 @@ server:
56
57
---
58
59
-[](<>)
59
+
collectors/python.d.plugin/icecast/README.md
+1
-1
@@ -41,4 +41,4 @@ Without configuration, module attempts to connect to `http://localhost:8443/stat
41
42
---
43
44
-[](<>)
44
+
collectors/python.d.plugin/ipfs/README.md
+1
-1
@@ -48,4 +48,4 @@ remote:
48
49
---
50
51
-[](<>)
51
+
collectors/python.d.plugin/isc_dhcpd/README.md
+1
-1
@@ -54,4 +54,4 @@ The module will not work If no configuration is given.
54
55
---
56
57
-[](<>)
57
+
collectors/python.d.plugin/litespeed/README.md
+1
-1
@@ -69,4 +69,4 @@ If no configuration is given, module will use "/tmp/lshttpd/".
69
70
---
71
72
-[](<>)
72
+
collectors/python.d.plugin/logind/README.md
+1
-1
@@ -83,4 +83,4 @@ sudo ./edit-config python.d/logind.conf
83
84
---
85
86
-[](<>)
86
+
collectors/python.d.plugin/megacli/README.md
+1
-1
@@ -83,4 +83,4 @@ do_battery: yes
83
Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate
84
method](/docs/configure/start-stop-restart.md) for your system.
85
86
-[](<>)
86
+
collectors/python.d.plugin/memcached/README.md
+1
-1
@@ -96,4 +96,4 @@ If no configuration is given, module will attempt to connect to memcached instan
96
97
---
98
99
-[](<>)
99
+
collectors/python.d.plugin/mongodb/README.md
+1
-1
@@ -207,4 +207,4 @@ If no configuration is given, module will attempt to connect to mongodb daemon o
207
208
---
209
210
-[](<>)
210
+
collectors/python.d.plugin/monit/README.md
+1
-1
@@ -49,4 +49,4 @@ If no configuration is given, module will attempt to connect to monit as `http:/
49
50
---
51
52
-[](<>)
52
+
collectors/python.d.plugin/mysql/README.md
+1
-1
@@ -393,4 +393,4 @@ page](https://mariadb.com/kb/en/library/user-statistics/)
393
394
---
395
396
-[](<>)
396
+
collectors/python.d.plugin/nginx/README.md
+1
-1
@@ -62,4 +62,4 @@ Without configuration, module attempts to connect to `http://localhost/stub_stat
62
63
---
64
65
-[](<>)
65
+
collectors/python.d.plugin/nginx_plus/README.md
+1
-1
@@ -162,4 +162,4 @@ Without configuration, module fail to start.
162
163
---
164
165
-[](<>)
165
+
collectors/python.d.plugin/nsd/README.md
+1
-1
@@ -65,4 +65,4 @@ Configuration is not needed.
65
66
---
67
68
-[](<>)
68
+
collectors/python.d.plugin/ntpd/README.md
+1
-1
@@ -87,4 +87,4 @@ If no configuration is given, module will attempt to connect to `ntpd` on `::1:1
87
88
---
89
90
-[](<>)
90
+
collectors/python.d.plugin/nvidia_smi/README.md
+1
-1
@@ -61,4 +61,4 @@ poll_seconds : 1
61
exclude_zero_memory_users : yes
62
```
63
64
-[](<>)
64
+
collectors/python.d.plugin/openldap/README.md
+1
-1
@@ -76,4 +76,4 @@ openldap:
76
77
---
78
79
-[](<>)
79
+
collectors/python.d.plugin/oracledb/README.md
+1
-1
@@ -94,4 +94,4 @@ remote:
94
95
All parameters are required. Without them module will fail to start.
96
97
-[](<>)
97
+
collectors/python.d.plugin/ovpn_status_log/README.md
+1
-1
@@ -47,4 +47,4 @@ default
47
48
---
49
50
-[](<>)
50
+
collectors/python.d.plugin/phpfpm/README.md
+1
-1
@@ -48,4 +48,4 @@ Without configuration, module attempts to connect to `http://localhost/status`
48
49
---
50
51
-[](<>)
51
+
collectors/python.d.plugin/portcheck/README.md
+1
-1
@@ -49,4 +49,4 @@ server:
49
50
---
51
52
-[](<>)
52
+
collectors/python.d.plugin/postfix/README.md
+1
-1
@@ -24,4 +24,4 @@ Configuration is not needed.
24
25
---
26
27
-[](<>)
27
+
collectors/python.d.plugin/postgres/README.md
+1
-1
@@ -115,4 +115,4 @@ tcp:
115
116
---
117
118
-[](<>)
118
+
collectors/python.d.plugin/powerdns/README.md
+1
-1
@@ -101,4 +101,4 @@ local:
101
102
---
103
104
-[](<>)
104
+
collectors/python.d.plugin/proxysql/README.md
+1
-1
@@ -103,4 +103,4 @@ If no configuration is given, module will fail to run.
103
104
---
105
106
-[](<>)
106
+
collectors/python.d.plugin/puppet/README.md
+1
-1
@@ -64,4 +64,4 @@ When no configuration is given, module uses `https://fqdn.example.com:8140`.
64
65
---
66
67
-[](<>)
67
+
collectors/python.d.plugin/rabbitmq/README.md
+1
-1
@@ -113,4 +113,4 @@ socket:
113
114
---
115
116
-[](<>)
116
+
collectors/python.d.plugin/redis/README.md
+1
-1
@@ -61,4 +61,4 @@ When no configuration file is found, module tries to connect to TCP/IP socket: `
61
62
---
63
64
-[](<>)
64
+
collectors/python.d.plugin/rethinkdbs/README.md
+1
-1
@@ -50,4 +50,4 @@ When no configuration file is found, module tries to connect to `127.0.0.1:28015
50
51
---
52
53
-[](<>)
53
+
collectors/python.d.plugin/retroshare/README.md
+1
-1
@@ -44,4 +44,4 @@ remote:
44
```
45
---
46
47
-[](<>)
47
+
collectors/python.d.plugin/riakkv/README.md
-2
@@ -124,5 +124,3 @@ With no explicit configuration given, the module will attempt to connect to
124
The default update frequency for the plugin is set to 2 seconds as Riak
125
internally updates the metrics every second. If we were to update the metrics
126
every second, the resulting graph would contain odd jitter.
127
-
128
-[]()
collectors/python.d.plugin/samba/README.md
+1
-1
@@ -118,4 +118,4 @@ sudo ./edit-config python.d/samba.conf
118
119
---
120
121
-[](<>)
121
+
collectors/python.d.plugin/sensors/README.md
+1
-1
@@ -28,4 +28,4 @@ Please join this discussion for help.
28
29
---
30
31
-[](<>)
31
+
collectors/python.d.plugin/smartd_log/README.md
+1
-1
@@ -122,4 +122,4 @@ If no configuration is given, module will attempt to read log files in `/var/log
122
123
---
124
125
-[](<>)
125
+
collectors/python.d.plugin/spigotmc/README.md
+1
-1
@@ -35,4 +35,4 @@ By default, a connection to port 25575 on the local system is attempted with an
35
36
---
37
38
-[](<>)
38
+
collectors/python.d.plugin/springboot/README.md
+1
-1
@@ -142,4 +142,4 @@ Please check
142
[springboot.conf](https://raw.githubusercontent.com/netdata/netdata/master/collectors/python.d.plugin/springboot/springboot.conf)
143
for more examples.
144
145
-[](<>)
145
+
collectors/python.d.plugin/squid/README.md
+1
-1
@@ -55,4 +55,4 @@ Without any configuration module will try to autodetect where squid presents its
55
56
---
57
58
-[](<>)
58
+
collectors/python.d.plugin/tomcat/README.md
+1
-1
@@ -50,4 +50,4 @@ So it will probably fail.
50
51
---
52
53
-[](<>)
53
+
collectors/python.d.plugin/tor/README.md
+1
-1
@@ -61,4 +61,4 @@ Without configuration, module attempts to connect to `127.0.0.1:9051`.
61
62
---
63
64
-[](<>)
64
+
collectors/python.d.plugin/traefik/README.md
+1
-1
@@ -71,4 +71,4 @@ Without configuration, module attempts to connect to `http://localhost:8080/heal
71
72
---
73
74
-[](<>)
74
+
collectors/python.d.plugin/uwsgi/README.md
+1
-1
@@ -49,4 +49,4 @@ localhost:
49
50
When no configuration file is found, module tries to connect to TCP/IP socket: `localhost:1717`.
51
52
-[](<>)
52
+
collectors/python.d.plugin/varnish/README.md
+1
-1
@@ -62,4 +62,4 @@ The name of the `varnishd` instance to get logs from. If not specified, the host
62
63
---
64
65
-[](<>)
65
+
collectors/python.d.plugin/w1sensor/README.md
+1
-1
@@ -25,4 +25,4 @@ sudo ./edit-config python.d/w1sensor.conf
25
26
---
27
28
-[](<>)
28
+
collectors/python.d.plugin/web_log/README.md
+1
-1
@@ -216,4 +216,4 @@ The column `minimum requests` state the minimum number of requests required for
216
217
Netdata alarms are user-configurable. Sample config files can be found under directory `health/health.d` of the [Netdata GitHub repository](https://github.com/netdata/netdata/).
218
219
-[](<>)
219
+
collectors/slabinfo.plugin/README.md
+1
-1
@@ -26,4 +26,4 @@ In the following screenshot, you can clearly see a `find` done on a ext4 filesys
26
27
28
29
-[](<>)
29
+
collectors/statsd.plugin/README.md
+1
-1
@@ -611,4 +611,4 @@ The function is smart enough to call `nc` just once and pass all the metrics to
611
612
If you have gotten thus far, make sure to check out our [community forums](https://community.netdata.cloud) to share your experience using Netdata with StatsD.
613
614
-[](<>)
614
+
collectors/tc.plugin/README.md
+1
-1
@@ -202,4 +202,4 @@ Finally, create `/etc/netdata/tc-qos-helper.conf` with this content:
202
203
Please note, that by default Netdata will enable monitoring metrics only when they are not zero. If they are constantly zero they are ignored. Metrics that will start having values, after Netdata is started, will be detected and charts will be automatically added to the dashboard (a refresh of the dashboard is needed for them to appear though). Set `yes` for a chart instead of `auto` to enable it permanently. You can also set the `enable zero metrics` option to `yes` in the `[global]` section which enables charts with zero metrics for all internal Netdata plugins.
204
205
-[](<>)
205
+
collectors/timex.plugin/README.md
+1
-1
@@ -26,4 +26,4 @@ Scroll down to the `[plugin:timex]` section to find the available options:
26
# time offset = yes
27
```
28
29
-[](<>)
29
+
collectors/xenstat.plugin/README.md
+1
-1
@@ -50,4 +50,4 @@ sudo /usr/libexec/netdata/plugins.d/xenstat.plugin 1 debug
50
51
You will get verbose output on what the plugin does.
52
53
-[](<>)
53
+
contrib/README.md
+1
-1
@@ -58,4 +58,4 @@ source is to remove the current package from your system, then
58
install the new package. Upgrading on wheezy is known to not
59
work cleanly; Jessie may behave as expected.
60
61
-[](<>)
61
+
contrib/sles11/README.md
+1
-1
@@ -14,4 +14,4 @@ changes and additions for sles 11 backport, namely:
14
- crude hack of notification script to work with bash 3 (email and syslog only, one destination,
15
see comments at the top)
16
17
-[](<>)
17
+
daemon/README.md
+1
-1
@@ -551,4 +551,4 @@ valgrind $(which netdata) -D
551
Netdata will start and it will be a lot slower. Now reproduce the crash and `valgrind` will dump on your console the
552
stack trace. Open a new github issue and post the output.
553
554
-[](<>)
554
+
daemon/config/README.md
+1
-1
@@ -227,4 +227,4 @@ multiplying the value of `out` by -1, Netdata creates the negative values seen i
227
229
230
-[](<>)
230
+
database/README.md
+1
-1
@@ -212,4 +212,4 @@ Netdata will create charts for kernel memory de-duplication performance, like th
212
213
214
215
-[](<>)
215
+
database/engine/README.md
+1
-1
@@ -256,4 +256,4 @@ and generate a read load of 1.7M/sec, whereas in the CPU-bound scenario the read
256
Consequently, there is a significant degree of interference by the reader threads, that slow down the writer threads.
257
This is also possible because the interference effects are greater than the SSD impact on data generation throughput.
258
259
-[](<>)
259
+
diagrams/data_structures/README.md
+1
-1
@@ -15,4 +15,4 @@ These are the main internal data structures of `netdata`. Created with `draw.io`
15
16
17
18
-[](<>)
18
+
docs/Add-more-charts-to-netdata.md
-2
@@ -11,5 +11,3 @@ This file has been deprecated. Please see our [collectors docs](/collectors/READ
11
12
See the [list of supported collectors](/collectors/COLLECTORS.md) to see all the sources Netdata can collect metrics
13
from.
14
-
15
-[]()
docs/Demo-Sites.md
+1
-1
@@ -22,4 +22,4 @@ You can also view live demos of Netdata at **[https://www.netdata.cloud](https:/
22
23
Netdata dashboards are mobile- and touch-friendly.
24
25
-[](<>)
25
+
docs/Donations-netdata-has-received.md
+1
-1
@@ -26,4 +26,4 @@ Thank you!
26
27
Please contact me at costa@tsaousis.gr.
28
29
-[](<>)
29
+
docs/README.md
+1
-1
@@ -14,4 +14,4 @@ perfect.
14
15
Now get out there and build an exceptional infrastructure.
16
17
-[](<>)
17
+
docs/Running-behind-apache.md
+1
-1
@@ -368,4 +368,4 @@ Make sure the requests reach Netdata, by examining `/var/log/netdata/access.log`
368
1. if the requests do not reach Netdata, your apache does not forward them.
369
2. if the requests reach Netdata but the URLs are wrong, you have not re-written them properly.
370
371
-[](<>)
371
+
docs/Running-behind-caddy.md
+1
-1
@@ -31,4 +31,4 @@ You would also need to instruct Netdata to listen only to `127.0.0.1` or `::1`.
31
32
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`.
33
34
-[](<>)
34
+
docs/Running-behind-haproxy.md
+1
-1
@@ -290,4 +290,4 @@ backend netdata_backend
290
http-request set-header Connection "keep-alive"
291
```
292
293
-[](<>)
293
+
docs/Running-behind-lighttpd.md
+1
-1
@@ -68,4 +68,4 @@ You would also need to instruct Netdata to listen only to `127.0.0.1` or `::1`.
68
69
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`.
70
71
-[](<>)
71
+
docs/Running-behind-nginx.md
+1
-1
@@ -267,4 +267,4 @@ If you get an 502 Bad Gateway error you might check your Nginx error log:
267
268
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`.
269
270
-[](<>)
270
+
docs/a-github-star-is-important.md
+1
-1
@@ -21,4 +21,4 @@ Thank you!
21
22
Costa Tsaousis
23
24
-[](<>)
24
+
docs/agent-cloud.md
-2
@@ -75,5 +75,3 @@ about how you might want to use or configure Cloud, we recommend the following:
75
onboarding and connect your first nodes.
76
- Better understand how agents connect securely to the Cloud with [connect agent to Cloud](/claim/README.md) and [Agent-Cloud
77
link](/aclk/README.md) documentation.
78
-
79
-[]()
docs/anonymous-statistics.md
-1
@@ -106,4 +106,3 @@ Prior to v1.29.4 we used Google Analytics to capture this information. This led
106
107
While we migrate fully away from Google Analytics to PostHog there maybe be a small period of time where we run both in parallel before we remove all Google Analytics related code. This is to ensure we can fully test and validate the Netdata PostHog implementation before fully defaulting to it.
108
109
-[]()
docs/collect/application-metrics.md
+1
-1
@@ -77,4 +77,4 @@ Collecting all the available metrics on your nodes, and across your entire infra
77
puzzle. Next, learn more about Netdata's famous real-time visualizations by [seeing an overview of your
78
infrastructure](/docs/visualize/overview-infrastructure.md) using Netdata Cloud.
79
80
-[](<>)
80
+
docs/collect/container-metrics.md
+1
-1
@@ -96,4 +96,4 @@ brokers, and more. See more in the [application metrics doc](/docs/collect/appli
96
If you already have all the information you need about collecting metrics, move into Netdata's meaningful visualizations
97
with [seeing an overview of your infrastructure](/docs/visualize/overview-infrastructure.md) using Netdata Cloud.
98
99
-[](<>)
99
+
docs/collect/enable-configure.md
+1
-1
@@ -65,4 +65,4 @@ Netdata's visualization features. [See an overview of your infrastructure](/docs
65
using Netdata Cloud, or learn how to [interact with dashboards and
66
charts](/docs/visualize/interact-dashboards-charts.md).
67
68
-[](<>)
68
+
docs/collect/how-collectors-work.md
+1
-1
@@ -77,4 +77,4 @@ your infrastructure.
77
See our [collectors reference](/collectors/REFERENCE.md) for detailed information on Netdata's collector architecture,
78
troubleshooting a collector, developing a custom collector, and more.
79
80
-[](<>)
80
+
docs/collect/system-metrics.md
+1
-1
@@ -63,4 +63,4 @@ should investigate Netdata's container compatibility if you use them heavily in
63
If you don't use containers, skip ahead to collecting [application metrics](/docs/collect/application-metrics.md) with
64
Netdata.
65
66
-[](<>)
66
+
docs/contributing/contributing-documentation.md
+1
-1
@@ -106,4 +106,4 @@ specific sections and ask for additional information or other fixes.
106
After merging your PR, the Netdata team rebuilds the [documentation site](https://learn.netdata.cloud) to publish the
107
changed documentation.
108
109
-[](<>)
109
+
docs/contributing/style-guide.md
+1
-1
@@ -489,4 +489,4 @@ The following tables describe the standard spelling, capitalization, and usage o
489
| **preconfigured** | The concept that many of Netdata's features come with sane defaults that users don't need to configure to find [immediate value](/docs/overview/why-netdata.md#simple-to-deploy). |
490
| **real time**/**real-time** | Use _real time_ as a noun phrase, most often with _in_: _Netdata collects metrics in real time_. Use _real-time_ as an adjective: _Netdata collects real-time metrics from hundreds of supported applications and services. |
491
492
-[](<>)
492
+
docs/export/enable-connector.md
+1
-1
@@ -92,4 +92,4 @@ labels](/docs/guides/using-host-labels.md) on exported metrics.
92
- [OpenTSDB connector](/exporting/opentsdb/README.md)
93
- [Graphite connector](/exporting/graphite/README.md)
94
95
-[](<>)
95
+
docs/export/external-databases.md
+1
-1
@@ -87,4 +87,4 @@ Graphite_](/docs/guides/export/export-netdata-metrics-graphite.md).
87
- [Exporting engine reference](/exporting/README.md)
88
- [Backends reference (deprecated)](/backends/README.md)
89
90
-[](<>)
90
+
docs/guides/collect-apache-nginx-web-logs.md
+1
-1
@@ -159,4 +159,4 @@ into powerful real-time tools for keeping your servers happy.
159
Don't forget to give GitHub user [Wing924](https://github.com/Wing924) a big 👍 for his hard work in starting up the Go
160
refactoring effort.
161
162
-[](<>)
162
+
docs/guides/collect-unbound-metrics.md
+1
-1
@@ -137,4 +137,4 @@ for improvement or refinement based on real-world use cases. Feel free to [file
137
issue](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml) with your
138
thoughts.
139
140
-[](<>)
140
+
docs/guides/deploy/ansible.md
+1
-1
@@ -171,4 +171,4 @@ provisioning/infrastructure as code software, such as Chef or Puppet, in our [co
171
repo](https://github.com/netdata/community). Anyone is able to fork the repo and submit a PR, either to improve this
172
playbook, extend it, or create an entirely new experience for deploying Netdata across entire infrastructure.
173
174
-[](<>)
174
+
docs/guides/export/export-netdata-metrics-graphite.md
+1
-1
@@ -180,4 +180,4 @@ often.
180
For full details about each configuration option and what it does, see the [exporting reference
181
guide](/exporting/README.md).
182
183
-[](<>)
183
+
docs/guides/longer-metrics-storage.md
+1
-1
@@ -157,4 +157,4 @@ charts](/web/README.md#using-charts).
157
And if you'd now like to reduce Netdata's resource usage, view our [performance
158
guide](/docs/guides/configure/performance.md) for our best practices on optimization.
159
160
-[](<>)
160
+
docs/guides/monitor-cockroachdb.md
+1
-1
@@ -133,4 +133,4 @@ Also, be sure to check out these useful resources:
133
- [Monitor CockroachDB with
134
Prometheus](https://www.cockroachlabs.com/docs/stable/monitor-cockroachdb-with-prometheus.html)
135
136
-[](<>)
136
+
docs/guides/monitor-hadoop-cluster.md
+1
-1
@@ -200,4 +200,4 @@ issue](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cnee
200
file](https://github.com/netdata/go.d.plugin/blob/master/config/go.d/zookeeper.conf) to understand how to configure
201
global options or per-job options, timeouts, TLS certificates, and more.
202
203
-[](<>)
203
+
docs/guides/monitor/dimension-templates.md
+1
-1
@@ -173,4 +173,4 @@ Or, at the very least, simplify your configuration files.
173
For information about other advanced features in Netdata's health monitoring toolkit, check out our [health
174
documentation](/health/README.md). And if you have some cool alarms you built using dimension templates,
175
176
-[](<>)
176
+
docs/guides/monitor/kubernetes-k8s-netdata.md
+1
-1
@@ -251,4 +251,4 @@ clusters of all sizes.
251
collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/k8s_kubeproxy)
252
- [Netdata Agent · `cgroups.plugin`](/collectors/cgroups.plugin/README.md)
253
254
-[](<>)
254
+
docs/guides/monitor/lamp-stack.md
-1
@@ -244,4 +244,3 @@ source of issues faster with [Metric Correlations](https://learn.netdata.cloud/d
244
- [Netdata Agent · MySQL data collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/mysql)
245
- [Netdata Agent · PHP-FPM data collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/phpfpm)
246
247
-[](<>)
\ No newline at end of file
docs/guides/monitor/pi-hole-raspberry-pi.md
+1
-1
@@ -159,4 +159,4 @@ troubleshooting the health of your systems and services.
159
If you have any questions about using Netdata to monitor your Raspberry Pi, Pi-hole, or any other applications, head on
160
over to our [community forum](https://community.netdata.cloud/).
161
162
-[](<>)
162
+
docs/guides/monitor/process.md
+1
-1
@@ -298,4 +298,4 @@ frameworks.
298
- [Netdata Agent · Dashboards](/web/README.md#dimensions)
299
- [Netdata Agent · MySQL collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/mysql)
300
301
-[](<>)
301
+
docs/guides/monitor/raspberry-pi-anomaly-detection.md
+1
-1
@@ -122,4 +122,4 @@ feedback on our [community forum](https://community.netdata.cloud/t/anomalies-co
122
- [Netdata Agent · Get Netdata](/docs/get-started.mdx)
123
- [Netdata Agent · Anomalies collector](/collectors/python.d.plugin/anomalies/README.md)
124
125
-[](<>)
125
+
docs/guides/monitor/statsd.md
+1
-1
@@ -295,4 +295,4 @@ Netdata allows you easily visualize any StatsD metric without any configuration,
295
296
- [Netdata Agent · StatsD](/collectors/statsd.plugin/README.md)
297
298
-[](<>)
298
+
docs/guides/monitor/stop-notifications-alarms.md
+1
-1
@@ -89,4 +89,4 @@ You can also use Netdata's [Health Management API](/web/api/health/README.md#hea
89
checks and notifications while Netdata runs. With this API, you can disable health checks during a maintenance window or
90
backup process, for example.
91
92
-[](<>)
92
+
docs/guides/monitor/visualize-monitor-anomalies.md
+1
-1
@@ -139,4 +139,4 @@ that works well for monitoring some other popular application, like MySQL, Postg
139
- [Netdata Agent · Anomalies collector](/collectors/python.d.plugin/anomalies/README.md)
140
- [Netdata Cloud · Build new dashboards](https://learn.netdata.cloud/docs/cloud/visualize/dashboards)
141
142
-[](<>)
142
+
docs/guides/python-collector.md
+1
-1
@@ -483,4 +483,4 @@ Now we you ready to start developing our Netdata python Collector and share it w
483
production-grade collectors.
484
- Celebrate! You have contributed to an open-source project with hundreds of thousands of users!
485
486
-[](<>)
486
+
docs/guides/step-by-step/step-00.md
+1
-1
@@ -117,4 +117,4 @@ MongoDB, TimescaleDB, and others.
117
118
Run Netdata behind an Nginx proxy to improve performance, and enable TLS/HTTPS for better security.
119
120
-[](<>)
120
+
docs/guides/step-by-step/step-01.md
+1
-1
@@ -153,4 +153,4 @@ get right into that dashboard you've heard so much about.
153
154
[Next: Get to know Netdata's dashboard →](step-02.md)
155
156
-[](<>)
156
+
docs/guides/step-by-step/step-02.md
+1
-1
@@ -205,4 +205,4 @@ Next, you'll learn how to monitor multiple nodes through the dashboard.
205
206
[Next: Monitor more than one system with Netdata →](step-03.md)
207
208
-[](<>)
208
+
docs/guides/step-by-step/step-03.md
+1
-1
@@ -88,4 +88,4 @@ customize your Netdata experience to your exact infrastructure and the informati
88
89
[Next: The basics of configuring Netdata →](step-04.md)
90
91
-[](<>)
91
+
docs/guides/step-by-step/step-04.md
+1
-1
@@ -141,4 +141,4 @@ choosing.
141
142
[Next: Health monitoring alarms and notifications →](step-05.md)
143
144
-[](<>)
144
+
docs/guides/step-by-step/step-05.md
+1
-1
@@ -347,4 +347,4 @@ from hundreds of services with almost no configuration on your part. Onward!
347
348
[Next: Collect metrics from more services and apps →](step-06.md)
349
350
-[](<>)
350
+
docs/guides/step-by-step/step-06.md
+1
-1
@@ -119,4 +119,4 @@ the dashboard to learn more about some of its more advanced features.
119
120
[Next: Netdata's dashboard in depth →](step-07.md)
121
122
-[](<>)
122
+
docs/guides/step-by-step/step-07.md
+1
-1
@@ -111,4 +111,4 @@ Next, you'll learn how to build your first custom dashboard!
111
112
[Next: Build your first custom dashboard →](step-08.md)
113
114
-[](<>)
114
+
docs/guides/step-by-step/step-08.md
+1
-1
@@ -392,4 +392,4 @@ Next, you'll learn how to store long-term historical metrics in Netdata!
392
393
[Next: Long-term metrics storage →](/docs/guides/step-by-step/step-09.md)
394
395
-[](<>)
395
+
docs/guides/step-by-step/step-09.md
+1
-1
@@ -159,4 +159,4 @@ our Netdata dashboard.
159
160
[Next: Set up a proxy →](/docs/guides/step-by-step/step-10.md)
161
162
-[](<>)
162
+
docs/guides/step-by-step/step-10.md
+1
-1
@@ -229,4 +229,4 @@ For some celebratory emoji and a clap on the back, head on over to our final ste
229
230
[Next: The end. →](step-99.md)
231
232
-[](<>)
232
+
docs/guides/step-by-step/step-99.md
+1
-1
@@ -48,4 +48,4 @@ If that feels like too much possibility to you, why not one of these options:
48
49
We can't wait to see what you monitor next! Bon voyage! ⛵
50
51
-[](<>)
51
+
docs/guides/troubleshoot/monitor-debug-applications-ebpf.md
+1
-1
@@ -267,4 +267,4 @@ we'd love to hear them: [info@netdata.cloud](mailto:info@netdata.cloud).
267
268
Happy troubleshooting!
269
270
-[](<>)
270
+
docs/guides/using-host-labels.md
+1
-1
@@ -209,4 +209,4 @@ If you have issues or questions around using host labels, don't hesitate to [fil
209
issue](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml) on GitHub. We're
210
excited to make host labels even more valuable to our users, which we can only do with your input.
211
212
-[](<>)
212
+
docs/monitor/configure-alarms.md
+1
-1
@@ -145,4 +145,4 @@ state.
145
146
To build complex, dynamic alarms, read our guide on [dimension templates](/docs/guides/monitor/dimension-templates.md).
147
148
-[](<>)
148
+
docs/monitor/enable-notifications.md
+1
-1
@@ -144,4 +144,4 @@ architecture](/docs/store/distributed-data-architecture.md) for the best-in-clas
144
- [Netdata Cloud · Alarm notifications](https://learn.netdata.cloud/docs/cloud/alerts-notifications/notifications)
145
- [Netdata Agent · Notifications](/health/notifications/README.md)
146
147
-[](<>)
147
+
docs/monitor/view-active-alarms.md
+1
-1
@@ -72,4 +72,4 @@ If you're happy with the pre-configured alarms, skip ahead to [enable
72
notifications](/docs/monitor/enable-notifications.md) to use Netdata Cloud's centralized alarm notifications and/or
73
per-node notifications to endpoints like Slack, PagerDuty, Twilio, and more.
74
75
-[](<>)
75
+
docs/netdata-for-IoT.md
+1
-1
@@ -71,4 +71,4 @@ Then restart Netdata. You will get this:
71
72
73
74
-[](<>)
74
+
docs/netdata-security.md
+1
-1
@@ -226,4 +226,4 @@ _actively_ contributing to Netdata's future.
226
| `/var/lib/netdata`|user `netdata`<br/>group `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.|
227
| `/var/log/netdata`|user `netdata`<br/>group `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.|
228
229
-[](<>)
229
+
docs/overview/netdata-monitoring-stack.md
+1
-1
@@ -59,4 +59,4 @@ charts, or use Netdata's health watchdog to send notifications whenever an anoma
59
Whether you're using Netdata standalone or as part of a larger monitoring stack, the next step is the same: [**Get
60
Netdata**](/docs/get-started.mdx).
61
62
-[](<>)
62
+
docs/overview/what-is-netdata.md
+1
-1
@@ -71,4 +71,4 @@ case:
71
Learn more about [why you should use Netdata](/docs/overview/why-netdata.md), or [how Netdata works with your existing
72
monitoring stack](/docs/overview/netdata-monitoring-stack.md).
73
74
-[](<>)
74
+
docs/overview/why-netdata.md
+1
-1
@@ -60,4 +60,4 @@ Whether you already have a monitoring stack you want to integrate Netdata into,
60
ground-up, you should read more on how Netdata can work either [standalone or as an interoperable part of a monitoring
61
stack](/docs/overview/netdata-monitoring-stack.md).
62
63
-[](<>)
63
+
docs/quickstart/infrastructure.md
+1
-1
@@ -182,4 +182,4 @@ To change how the Netdata Agent runs on each node, dig in to configuration files
182
GitHub](https://learn.netdata.cloud/docs/cloud/manage/sign-in)
183
- [Netdata Cloud · Nodes view](https://learn.netdata.cloud/docs/cloud/visualize/nodes)
184
185
-[](<>)
185
+
docs/quickstart/single-node.md
+1
-1
@@ -89,4 +89,4 @@ out some of Netdata's other visualization and health monitoring features:
89
- [Export metrics](/docs/export/external-databases.md) to an external time-series database to use Netdata alongside
90
other monitoring and troubleshooting tools.
91
92
-[](<>)
92
+
docs/store/change-metrics-storage.md
+1
-1
@@ -74,4 +74,4 @@ further analysis, visualization, or correlation with other tools.
74
75
- [Netdata Agent · Database engine](/database/engine/README.md)
76
77
-[](<>)
77
+
docs/store/distributed-data-architecture.md
+1
-1
@@ -68,4 +68,4 @@ You can configure the Netdata Agent to store days, weeks, or months worth of dis
68
resources required to retain your desired amount of metrics, and expand or contract the database by editing a single
69
setting.
70
71
-[](<>)
71
+
docs/visualize/create-dashboards.md
+1
-1
@@ -61,4 +61,4 @@ While it's useful to see real-time metrics on flexible dashboards, you need ways
61
strikes. Every Netdata Agent comes with a health watchdog that uses [alarms](/docs/monitor/configure-alarms.md) and
62
[notifications](/docs/monitor/enable-notifications.md) to notify you of issues seconds after they strike.
63
64
-[](<>)
64
+
docs/visualize/interact-dashboards-charts.md
+1
-1
@@ -128,4 +128,4 @@ to get informed when something goes wrong in your infrastructure.
128
- [Netdata Cloud · Nodes](https://learn.netdata.cloud/docs/cloud/visualize/nodes)
129
- [Netdata Cloud · Build new dashboards](https://learn.netdata.cloud/docs/cloud/visualize/dashboards)
130
131
-[](<>)
131
+
docs/visualize/overview-infrastructure.md
+1
-1
@@ -108,4 +108,4 @@ visualizations_](/docs/guides/monitor/kubernetes-k8s-netdata.md), for a full wal
108
- [Netdata Cloud · Nodes view](https://learn.netdata.cloud/docs/cloud/visualize/nodes)
109
- [Netdata Cloud · Kubernetes visualizations](https://learn.netdata.cloud/docs/cloud/visualize/kubernetes)
110
111
-[](<>)
111
+
docs/why-netdata/1s-granularity.md
+1
-1
@@ -56,4 +56,4 @@ Netdata has been designed to:
56
57
So, for Netdata 1s granularity is easy, the natural outcome...
58
59
-[](<>)
59
+
docs/why-netdata/README.md
+1
-1
@@ -32,4 +32,4 @@ Netdata's helps us troubleshoot slowdowns without touching the console.
32
33
So, everything is a bit different.
34
35
-[](<>)
35
+
docs/why-netdata/immediate-results.md
+1
-1
@@ -43,4 +43,4 @@ Netdata:
43
- Does not introduce any query languages or any other technology to be learned. Of course some familiarity with the tool is required, but nothing too complicated.
44
- Includes all the community expertise and experience for monitoring systems and applications.
45
46
-[](<>)
46
+
docs/why-netdata/meaningful-presentation.md
+1
-1
@@ -65,4 +65,4 @@ But it simplifies everything else. Data collection, metrics database and visuali
65
66
Netdata goes a step further, by enriching the dashboard with information that is useful for most people. So, to improve clarity and help users be more effective, Netdata includes right in the dashboard the community knowledge and expertise about the metrics. So, that Netdata users can focus on solving their infrastructure problem, not on the technicalities of data collection and visualization.
67
68
-[](<>)
68
+
docs/why-netdata/unlimited-metrics.md
+1
-1
@@ -46,4 +46,4 @@ Due to Netdata's distributed nature, the number of metrics collected does not ha
46
47
Of course, since Netdata is also about [meaningful presentation](meaningful-presentation.md), the number of metrics makes Netdata development slower. We, the Netdata developers, need to have a good understanding of the metrics before adding them into Netdata. We need to organize the metrics, add information related to them, configure alarms for them, so that you, the Netdata users, will have the best out-of-the-box experience and all the information required to kill the console for troubleshooting slowdowns.
48
49
-[](<>)
49
+
exporting/README.md
+1
-1
@@ -311,4 +311,4 @@ Netdata adds 3 alarms:
311
312
313
314
-[](<>)
314
+
exporting/TIMESCALE.md
+1
-1
@@ -66,4 +66,4 @@ blog](https://blog.timescale.com/blog/writing-it-metrics-from-netdata-to-timesca
66
Thank you to Mahlon, Rune, TimescaleDB, and the members of the Netdata community that requested and then built this
67
exporting connection between Netdata and TimescaleDB!
68
69
-[](<>)
69
+
exporting/WALKTHROUGH.md
+1
-1
@@ -263,4 +263,4 @@ achieved you do not have to think about the monitoring system until Prometheus c
263
happens there are options presented in the Prometheus documentation for solving this. Hope this was helpful, happy
264
monitoring.
265
266
-[](<>)
266
+
exporting/aws_kinesis/README.md
+1
-1
@@ -55,4 +55,4 @@ Alternatively, you can set AWS credentials for the `netdata` user using AWS SDK
55
Netdata automatically computes a partition key for every record with the purpose to distribute records across
56
available shards evenly.
57
58
-[](<>)
58
+
exporting/graphite/README.md
+1
-1
@@ -32,4 +32,4 @@ Add `:http` or `:https` modifiers to the connector type if you need to use other
32
The Graphite connector is further configurable using additional settings. See the [exporting reference
33
doc](/exporting/README.md#options) for details.
34
35
-[](<>)
35
+
exporting/json/README.md
+1
-1
@@ -32,4 +32,4 @@ Add `:http` or `:https` modifiers to the connector type if you need to use other
32
The JSON connector is further configurable using additional settings. See the [exporting reference
33
doc](/exporting/README.md#options) for details.
34
35
-[](<>)
35
+
exporting/mongodb/README.md
+1
-1
@@ -35,4 +35,4 @@ You can find more information about the `destination` string URI format in the M
35
The default socket timeout depends on the exporting connector update interval. The timeout is 500 ms shorter than the
36
interval (but not less than 1000 ms). You can alter the timeout using the `sockettimeoutms` MongoDB URI option.
37
38
-[](<>)
38
+
exporting/opentsdb/README.md
+1
-1
@@ -32,4 +32,4 @@ Add `:http` or `:https` modifiers to the connector type if you need to use other
32
The OpenTSDB connector is further configurable using additional settings. See the [exporting reference
33
doc](/exporting/README.md#options) for details.
34
35
-[](<>)
35
+
exporting/prometheus/README.md
+1
-1
@@ -458,4 +458,4 @@ through a web proxy, or when multiple Prometheus servers are NATed to a single I
458
`&server=NAME` to the URL. This `NAME` is used by Netdata to uniquely identify each Prometheus server and keep track of
459
its last access time.
460
461
-[](<>)
461
+
exporting/prometheus/remote_write/README.md
+1
-1
@@ -55,4 +55,4 @@ buffer size on failures.
55
56
The remote write exporting connector does not support `buffer on failures`
57
58
-[](<>)
58
+
exporting/pubsub/README.md
+1
-1
@@ -35,4 +35,4 @@ Next, create the credentials JSON file by following Google Cloud's [authenticati
35
`chmod 400 google_cloud_credentials.json; chown netdata google_cloud_credentials.json`. Set the `credentials file`
36
option to the full path of the file.
37
38
-[](<>)
38
+
health/QUICKSTART.md
+1
-1
@@ -140,4 +140,4 @@ Or, get guided insights into specific health configurations with our [health gui
140
Finally, move on to Netdata's [notification system](/health/notifications/README.md) to learn more about how Netdata can
141
let you know when the health of your systems or apps goes awry.
142
143
-[](<>)
143
+
health/README.md
+1
-1
@@ -35,4 +35,4 @@ content.
35
**[Notifications](/health/notifications/README.md)**: Get notified about ongoing alarms from your Agents via your
36
favorite platform(s), such as Slack, Discord, PagerDuty, email, and much more.
37
38
-[](<>)
38
+
health/REFERENCE.md
+1
-1
@@ -913,4 +913,4 @@ to temporary disable notifications (for instance when running backups triggers a
913
notifications are runtime. The health checks can be controlled at runtime via the [health management
914
api](/web/api/health/README.md).
915
916
-[](<>)
916
+
health/notifications/README.md
+1
-1
@@ -83,4 +83,4 @@ bash -x /usr/libexec/netdata/plugins.d/alarm-notify.sh test
83
```
84
85
Then look in the output for the alarm-notify.sh calls and run the one you want to trace with `bash -x`.
86
-[](<>)
86
+
health/notifications/alerta/README.md
+1
-1
@@ -78,4 +78,4 @@ We can test alarms using the standard approach:
78
79
For more information see the [Alerta documentation](https://docs.alerta.io)
80
81
-[](<>)
81
+
health/notifications/awssns/README.md
+1
-1
@@ -40,4 +40,4 @@ Notes:
40
- 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 variables you can use in custom notifications.
41
- While Amazon SNS supports sending differently formatted messages for different delivery methods, Netdata does not currently support this functionality.
42
43
-[](<>)
43
+
health/notifications/custom/README.md
+1
-1
@@ -89,4 +89,4 @@ The following are more human friendly:
89
- `${severity}` like "Escalated to CRITICAL", "Recovered from WARNING"
90
- `${raised_for}` like "(alarm was raised for 10 minutes)"
91
92
-[](<>)
92
+
health/notifications/discord/README.md
+1
-1
@@ -47,4 +47,4 @@ role_recipients_discord[webmaster]="marketing development"
47
48
The keywords `systems`, `databases`, `marketing`, `development` are discordapp.com channels (they should already exist within your discord server).
49
50
-[](<>)
50
+
health/notifications/dynatrace/README.md
-2
@@ -32,5 +32,3 @@ The default value is `CUSTOM_INFO`.
32
This is a required parameter.
33
6. Specify the annotation type. This is the source of the Dynatrace event. Put whatever it fits you, for example,
34
_Netdata Alarm_, which is also the default value.
35
-
36
-[]()
health/notifications/email/README.md
+1
-1
@@ -74,4 +74,4 @@ sendmail="/usr/bin/msmtp"
74
chmod 600 ~/.msmtprc
75
```
76
77
-[](<>)
77
+
health/notifications/flock/README.md
+1
-1
@@ -34,4 +34,4 @@ FLOCK_WEBHOOK_URL="https://api.flock.com/hooks/sendMessage/XXXXXXXXXXXXXXXXXXXXX
34
DEFAULT_RECIPIENT_FLOCK="alarms"
35
```
36
37
-[](<>)
37
+
health/notifications/hangouts/README.md
+1
-1
@@ -52,4 +52,4 @@ You can define multiple rooms like this: `sysadmin devops alarms|critical`.
52
53
The keywords `sysadmin`, `devops`, and `alarms` are Hangouts rooms.
54
55
-[](<>)
55
+
health/notifications/irc/README.md
+1
-1
@@ -75,4 +75,4 @@ role_recipients_irc[webmaster]="#networking-alarms"
75
76
The keywords `#user-alarms`, `#networking-alarms`, `#system-alarms`, `#databases-alarms` are irc channels which belong to the specified IRC network.
77
78
-[](<>)
78
+
health/notifications/kavenegar/README.md
+1
-1
@@ -43,4 +43,4 @@ KAVENEGAR_SENDER=""
43
DEFAULT_RECIPIENT_KAVENEGAR=""
44
```
45
46
-[](<>)
46
+
health/notifications/matrix/README.md
+1
-1
@@ -55,4 +55,4 @@ MATRIX_ACCESSTOKEN="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
55
DEFAULT_RECIPIENT_MATRIX="!XXXXXXXXXXXX:matrix.org"
56
```
57
58
-[](<>)
58
+
health/notifications/messagebird/README.md
+1
-1
@@ -42,4 +42,4 @@ MESSAGEBIRD_NUMBER="XXXXXXX"
42
DEFAULT_RECIPIENT_MESSAGEBIRD="XXXXXXX"
43
```
44
45
-[](<>)
45
+
health/notifications/msteams/README.md
+1
-1
@@ -42,4 +42,4 @@ role_recipients_msteams[dba]="YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY"
42
role_recipients_msteams[webmaster]="ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ"
43
```
44
45
-[](<>)
45
+
health/notifications/opsgenie/README.md
+1
-1
@@ -59,4 +59,4 @@ message:
59
You can find more details about the Opsgenie error codes in their [response
60
docs](https://docs.opsgenie.com/docs/response).
61
62
-[](<>)
62
+
health/notifications/prowl/README.md
-2
@@ -25,5 +25,3 @@ the Prowl website after registering.
25
26
Once you have an API key, simply specify that as a recipient for Prowl
27
notifications.
28
-
29
-[]()
health/notifications/pushbullet/README.md
+1
-1
@@ -47,4 +47,4 @@ PUSHBULLET_ACCESS_TOKEN="o.Sometokenhere"
47
DEFAULT_RECIPIENT_PUSHBULLET="admin1@example.com admin3@somemail.com #examplechanneltag #anotherchanneltag"
48
```
49
50
-[](<>)
50
+
health/notifications/pushover/README.md
+1
-1
@@ -20,4 +20,4 @@ pushover.net notifications look like this:
20
21
22
23
-[](<>)
23
+
health/notifications/rocketchat/README.md
+1
-1
@@ -49,4 +49,4 @@ role_recipients_rocketchat[webmaster]="marketing development"
49
The keywords `systems`, `databases`, `marketing`, `development` are RocketChat channels (they should already exist).
50
Both public and private channels can be used, even if they differ from the channel configured in your RocketChat incoming webhook.
51
52
-[](<>)
52
+
health/notifications/slack/README.md
+1
-1
@@ -47,4 +47,4 @@ role_recipients_slack[dba]="databases systems"
47
role_recipients_slack[webmaster]="marketing development"
48
```
49
50
-[](<>)
50
+
health/notifications/smstools3/README.md
+1
-1
@@ -41,4 +41,4 @@ Netdata uses the script `sendsms` that is installed by `smstools3` and just pass
41
sendsms=""
42
```
43
44
-[](<>)
44
+
health/notifications/stackpulse/README.md
+1
-1
@@ -78,4 +78,4 @@ access the **TRIGGER** tab to define the scenarios used to trigger the event. Th
78
79
For more details how to create a scenario, take a look at the [StackPulse documentation](https://docs.stackpulse.io).
80
81
-[](<>)
81
+
health/notifications/syslog/README.md
+1
-1
@@ -31,4 +31,4 @@ The `facility` and `level` are the standard syslog facility and level options, f
31
32
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).
33
34
-[](<>)
34
+
health/notifications/telegram/README.md
+1
-1
@@ -42,4 +42,4 @@ Telegram messages look like this:
42
43
44
45
-[](<>)
45
+
health/notifications/twilio/README.md
+1
-1
@@ -44,4 +44,4 @@ TWILIO_NUMBER="xxxxxxxxxxx"
44
DEFAULT_RECIPIENT_TWILIO="+15555555555"
45
```
46
47
-[](<>)
47
+
health/notifications/web/README.md
+1
-1
@@ -10,4 +10,4 @@ The Netdata dashboard shows HTML notifications, when it is open.
10
Such web notifications look like this:
11
12
13
-[](<>)
13
+
libnetdata/README.md
+1
-1
@@ -7,4 +7,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/READM
7
8
`libnetdata` is a collection of library code that is used by all Netdata `C` programs.
9
10
-[](<>)
10
+
libnetdata/adaptive_resortable_list/README.md
+1
-1
@@ -96,4 +96,4 @@ Compared to unoptimized code (test No 1: 4.6sec):
96
Do not use ARL if the a name/keyword may appear more than once in the
97
source data.
98
99
-[](<>)
99
+
libnetdata/avl/README.md
+1
-1
@@ -14,4 +14,4 @@ use any memory allocations and their memory footprint is optimized
14
15
In addition to the above, this version of AVL, provides versions using locks
16
and traversal functions.
17
-[](<>)
17
+
libnetdata/buffer/README.md
+1
-1
@@ -14,4 +14,4 @@ is just a lookup (it does not traverse the string).
14
15
Netdata uses `BUFFER`s for preparing web responses and buffering data to be sent upstream or
16
to backend databases.
17
-[](<>)
17
+
libnetdata/circular_buffer/README.md
-2
@@ -8,5 +8,3 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/circu
8
`struct circular_buffer` is an adaptive circular buffer. It will start at an initial size
9
and grow up to a maximum size as it fills. Two indices within the structure track the current
10
`read` and `write` position for data.
11
-
12
-[]()
libnetdata/clocks/README.md
+1
-1
@@ -2,4 +2,4 @@
2
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/clocks/README.md
3
-->
4
5
-[](<>)
5
+
libnetdata/config/README.md
+1
-1
@@ -51,4 +51,4 @@ When you get the configuration file from the server, there will be a
51
comment above all `name = value` pairs the server does not use.
52
So you know that whatever you wrote there, is not used.
53
54
-[](<>)
54
+
libnetdata/dictionary/README.md
+1
-1
@@ -2,4 +2,4 @@
2
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/dictionary/README.md
3
-->
4
5
-[](<>)
5
+
libnetdata/ebpf/README.md
+1
-1
@@ -2,4 +2,4 @@
2
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/ebpf/README.md
3
-->
4
5
-[](<>)
5
+
libnetdata/eval/README.md
+1
-1
@@ -1 +1 @@
1
-[](<>)
1
+
libnetdata/json/README.md
+1
-1
@@ -7,4 +7,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/json/
7
8
`json` contains a parser for json strings, based on `jsmn` (<https://github.com/zserge/jsmn>), but case you have installed the JSON-C library, the installation script will prefer it, you can also force its use with `--enable-jsonc` in the compilation time.
9
10
-[](<>)
10
+
libnetdata/locks/README.md
+1
-1
@@ -2,4 +2,4 @@
2
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/locks/README.md
3
-->
4
5
-[](<>)
5
+
libnetdata/log/README.md
+1
-1
@@ -2,4 +2,4 @@
2
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/log/README.md
3
-->
4
5
-[](<>)
5
+
libnetdata/popen/README.md
+1
-1
@@ -2,4 +2,4 @@
2
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/popen/README.md
3
-->
4
5
-[](<>)
5
+
libnetdata/procfile/README.md
+1
-1
@@ -64,4 +64,4 @@ and the data are inside the processor's caches.
64
65
This library is extensively used in Netdata and its plugins.
66
67
-[](<>)
67
+
libnetdata/simple_pattern/README.md
+1
-1
@@ -40,4 +40,4 @@ Netdata stops processing to the first positive or negative match
40
(left to right). If it is not matched by either positive or negative
41
patterns, it is denied at the end.
42
43
-[](<>)
43
+
libnetdata/socket/README.md
+1
-1
@@ -2,4 +2,4 @@
2
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/socket/README.md
3
-->
4
5
-[](<>)
5
+
libnetdata/statistical/README.md
+1
-1
@@ -2,4 +2,4 @@
2
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/statistical/README.md
3
-->
4
5
-[](<>)
5
+
libnetdata/storage_number/README.md
+1
-1
@@ -14,4 +14,4 @@ have less decimal precision) and 3 bits for flags.
14
15
This provides an extremely optimized memory footprint with just 0.0001% max accuracy loss.
16
17
-[](<>)
17
+
libnetdata/threads/README.md
+1
-1
@@ -2,4 +2,4 @@
2
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/threads/README.md
3
-->
4
5
-[](<>)
5
+
libnetdata/url/README.md
+1
-1
@@ -2,4 +2,4 @@
2
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/url/README.md
3
-->
4
5
-[](<>)
5
+
packaging/docker/README.md
+1
-1
@@ -489,4 +489,4 @@ Once you have contacted the Netdata owners to setup you up on Github and Travis,
489
Having followed these instructions, your forked repository should be all set up for integration with Travis CI. Happy
490
testing!
491
492
-[](<>)
492
+
packaging/installer/README.md
+1
-1
@@ -220,4 +220,4 @@ Our current build process has some issues when using certain configurations of t
220
section on `nonrepresentable section on output`
221
errors](/packaging/installer/methods/manual.md#nonrepresentable-section-on-output-errors) for a workaround.
222
223
-[](<>)
223
+
packaging/installer/REINSTALL.md
+1
-1
@@ -33,4 +33,4 @@ installer](/packaging/installer/methods/kickstart.md).
33
You can also post to our [community forums](https://community.netdata.cloud/c/support/13) or create a new [bug
34
report](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml).
35
36
-[](<>)
36
+
packaging/installer/UNINSTALL.md
+1
-1
@@ -51,4 +51,4 @@ The default `environment_file` is `/etc/netdata/.environment`.
51
> Note: This uninstallation method assumes previous installation with `netdata-installer.sh` or the kickstart script.
52
> Currently using it when Netdata was installed by a package manager can work or cause unexpected results.
53
54
-[](<>)
54
+
packaging/installer/UPDATE.md
+1
-1
@@ -117,4 +117,4 @@ sudo ./netdata-installer.sh
117
> ⚠️ If you installed Netdata with any optional parameters, such as `--no-updates` to disable automatic updates, and
118
> want to retain those settings, you need to set them again during this process.
119
120
-[](<>)
120
+
packaging/installer/methods/cloud-providers.md
+1
-1
@@ -123,4 +123,4 @@ Name: Netdata
123
124
Click **Add** to apply your new inbound security rule.
125
126
-[](<>)
126
+
packaging/installer/methods/freebsd.md
+1
-1
@@ -105,4 +105,4 @@ The `netdata-updater.sh` script will update your Agent.
105
| `--zlib-is-really-here` or `--libs-are-really-here` | If you get errors about missing zlib or libuuid but you know it is available, you might have a broken pkg-config. Use this option to proceed without checking pkg-config|
106
|`--disable-telemetry` | Use this flag to opt-out from our anonymous telemetry program. (DISABLE_TELEMETRY=1)|
107
108
-[](<>)
108
+
packaging/installer/methods/freenas.md
+1
-1
@@ -21,4 +21,4 @@ To start the Netdata service:
21
service netdata start
22
```
23
24
-[](<>)
24
+
packaging/installer/methods/kickstart.md
+1
-1
@@ -152,4 +152,4 @@ Read through Netdata's [documentation](https://learn.netdata.cloud/docs), which
152
solutions, to enable features like health monitoring, alarm notifications, long-term metrics storage, exporting to
153
external databases, and more.
154
155
-[](<>)
155
+
packaging/installer/methods/kubernetes.md
+1
-1
@@ -194,4 +194,4 @@ utilization metrics, and application metrics.
194
- [Netdata Helm chart](https://github.com/netdata/helmchart)
195
- [Netdata service discovery](https://github.com/netdata/agent-service-discovery/)
196
197
-[](<>)
197
+
packaging/installer/methods/macos.md
+1
-1
@@ -108,4 +108,4 @@ When you're finished with installation, check out our [single-node](/docs/quicks
108
Or, skip straight to [configuring the Netdata Agent](/docs/configure/nodes.md).
109
110
111
-[](<>)
111
+
packaging/installer/methods/manual.md
+1
-1
@@ -244,4 +244,4 @@ Read through Netdata's [documentation](https://learn.netdata.cloud/docs), which
244
solutions, to enable features like health monitoring, alarm notifications, long-term metrics storage, exporting to
245
external databases, and more.
246
247
-[](<>)
247
+
packaging/installer/methods/offline.md
-2
@@ -86,5 +86,3 @@ Or, skip straight to [configuring the Netdata Agent](/docs/configure/nodes.md).
86
Read through Netdata's [documentation](https://learn.netdata.cloud/docs), which is structured based on actions and
87
solutions, to enable features like health monitoring, alarm notifications, long-term metrics storage, exporting to
88
external databases, and more.
89
-
90
-[]()
packaging/installer/methods/pfsense.md
+1
-1
@@ -81,4 +81,4 @@ workaround from <https://redmine.pfsense.org/issues/6643>
81
82
**Note:** In pfSense, the Netdata configuration files are located under `/usr/local/etc/netdata`.
83
84
-[](<>)
84
+
packaging/installer/methods/source.md
+1
-1
@@ -234,4 +234,4 @@ repository](https://github.com/netdata/kernel-collector/blob/master/README.md),
234
which outlines both the required dependencies, as well as multiple
235
options for building the code.
236
237
-[](<>)
237
+
packaging/installer/methods/synology.md
+1
-1
@@ -58,4 +58,4 @@ installed. You'll have to do this manually:
58
59
3. Make sure `/etc/rc.netdata` is executable: `chmod 0755 /etc/rc.netdata`.
60
61
-[](<>)
61
+
packaging/maintainers/README.md
+1
-1
@@ -83,4 +83,4 @@ This page tracks the package maintainers for Netdata, for various operating syst
83
84
[](https://repology.org/metapackage/netdata/versions)
85
86
-[](<>)
86
+
packaging/makeself/README.md
+1
-1
@@ -51,4 +51,4 @@ To stop Netdata while it runs under `valgrind`, press Control-C on the console.
51
52
> 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 apply its heuristics and prints them.
53
54
-[](<>)
54
+
parser/README.md
-2
@@ -145,5 +145,3 @@ Output
145
146
Returns
147
- none
148
-
149
-[]()
registry/README.md
+1
-1
@@ -211,4 +211,4 @@ ERROR 409: Cannot ACCESS netdata registry: https://registry.my-netdata.io respon
211
212
This error is printed on your web browser console (press F12 on your browser to see it).
213
214
-[](<>)
214
+
streaming/README.md
+1
-1
@@ -727,4 +727,4 @@ file descriptor given is not a valid stream
727
728
After logging this error, Netdata will close the stream.
729
730
-[](<>)
730
+
tests/README.md
+1
-1
@@ -145,4 +145,4 @@ The karma and node.d runners can be integrated in Travis (AFAIK), but that is ou
145
146
Note: Karma is for browser-testing. On a build server, no GUI or browser might by available, unless browsers support headless mode.
147
148
-[](<>)
148
+
tests/health_mgmtapi/README.md
+1
-1
@@ -12,4 +12,4 @@ The script can be executed with options to prepare the system for the tests, run
12
It depends on the management API being accessible on localhost:19999 and on the responses to the api/v1/alarms?all requests being functional.
13
It also requires read access to the management API key that is usually under `/var/lib/netdata/netdata.api.key` (`@varlibdir_POST@/netdata.api.key`).
14
15
-[](<>)
15
+
web/README.md
-2
@@ -232,5 +232,3 @@ make
232
If you make any changes to the `src` directory when developing Netdata, you
233
should regenerate the `dashboard.js` file before you commit to the Netdata
234
repository.
235
-
236
-[]()
web/api/README.md
+1
-1
@@ -11,4 +11,4 @@ The complete documentation of the Netdata API is available at the **[Swagger Edi
11
12
If your prefer it over the Swagger Editor, you can also use **[Swagger UI](https://registry.my-netdata.io/swagger/#!/default/get_data)**. This however does not provide all the information available.
13
14
-[](<>)
14
+
web/api/badges/README.md
+1
-1
@@ -360,4 +360,4 @@ You can refresh them from your browser console though. Press F12 to open the web
360
var len = document.images.length; while(len--) { document.images[len].src = document.images[len].src.replace(/\?cacheBuster=\d*/, "") + "?cacheBuster=" + new Date().getTime().toString(); };
361
```
362
363
-[](<>)
363
+
web/api/exporters/README.md
+1
-1
@@ -7,4 +7,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/web/api/exporter
7
8
TBD
9
10
-[](<>)
10
+
web/api/exporters/prometheus/README.md
+1
-1
@@ -7,4 +7,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/web/api/exporter
7
8
Read the Prometheus exporter documentation: [Using Netdata with Prometheus](/exporting/prometheus/README.md).
9
10
-[](<>)
10
+
web/api/exporters/shell/README.md
+1
-1
@@ -66,4 +66,4 @@ NETDATA_${chart_id^^}_${dimension_id^^}="${value}"
66
67
The value is rounded to the closest integer, since shell script cannot process decimal numbers.
68
69
-[](<>)
69
+
web/api/formatters/README.md
+1
-1
@@ -75,4 +75,4 @@ For example, to download a CSV file with CPU utilization of the last hour,
75
This is done by appending `&tqx=outFileName:FILENAME` to any data query.
76
The output will be in the format given with `&format=`.
77
78
-[](<>)
78
+
web/api/formatters/csv/README.md
+1
-1
@@ -141,4 +141,4 @@ And this is how it looks when formatted:
141
| 2018-10-27 03:44:00 | 7026.9852167 |
142
| 2018-10-27 03:43:00 | 205.9904794 |
143
144
-[](<>)
144
+
web/api/formatters/json/README.md
+1
-1
@@ -153,4 +153,4 @@ google.visualization.Query.setResponse({version:'0.6',reqId:'0',status:'ok',sig:
153
}});
154
```
155
156
-[](<>)
156
+
web/api/formatters/ssv/README.md
+1
-1
@@ -56,4 +56,4 @@ in a JSON array:
56
[278,258,268,239,259,260,243,266,278,318,264,258]
57
```
58
59
-[](<>)
59
+
web/api/formatters/value/README.md
+1
-1
@@ -21,4 +21,4 @@ The Value formatter is not exposed by the API by itself.
21
Instead it is used by the [`ssv`](/web/api/formatters/ssv/README.md) formatter
22
and [health monitoring queries](/health/README.md).
23
24
-[](<>)
24
+
web/api/health/README.md
+1
-1
@@ -222,4 +222,4 @@ The file's location is configurable in `netdata.conf`. The default is shown belo
222
223
The test script under [tests/health_mgmtapi](/tests/health_mgmtapi/README.md) contains a series of tests that you can either run or read through to understand the various calls and responses better.
224
225
-[](<>)
225
+
web/api/queries/README.md
+1
-1
@@ -173,4 +173,4 @@ So, the proper way to query the database is to also set at least `after`. The fo
173
174
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.
175
176
-[](<>)
176
+
web/api/queries/average/README.md
+1
-1
@@ -43,4 +43,4 @@ Examining last 1 minute `successful` web server responses:
43
44
- <https://en.wikipedia.org/wiki/Average>.
45
46
-[](<>)
46
+
web/api/queries/des/README.md
+1
-1
@@ -70,4 +70,4 @@ Examining last 1 minute `successful` web server responses:
70
71
- <https://en.wikipedia.org/wiki/Exponential_smoothing>.
72
73
-[](<>)
73
+
web/api/queries/incremental_sum/README.md
+1
-1
@@ -38,4 +38,4 @@ Examining last 1 minute `successful` web server responses:
38
39
- none
40
41
-[](<>)
41
+
web/api/queries/max/README.md
+1
-1
@@ -35,4 +35,4 @@ Examining last 1 minute `successful` web server responses:
35
36
- <https://en.wikipedia.org/wiki/Sample_maximum_and_minimum>.
37
38
-[](<>)
38
+
web/api/queries/median/README.md
+1
-1
@@ -42,4 +42,4 @@ Examining last 1 minute `successful` web server responses:
42
43
- <https://en.wikipedia.org/wiki/Median>.
44
45
-[](<>)
45
+
web/api/queries/min/README.md
+1
-1
@@ -35,4 +35,4 @@ Examining last 1 minute `successful` web server responses:
35
36
- <https://en.wikipedia.org/wiki/Sample_maximum_and_minimum>.
37
38
-[](<>)
38
+
web/api/queries/ses/README.md
+1
-1
@@ -58,4 +58,4 @@ Examining last 1 minute `successful` web server responses:
58
- <https://en.wikipedia.org/wiki/Moving_average#exponential-moving-average>
59
- <https://en.wikipedia.org/wiki/Exponential_smoothing>.
60
61
-[](<>)
61
+
web/api/queries/stddev/README.md
+1
-1
@@ -90,4 +90,4 @@ Examining last 1 minute `successful` web server responses:
90
91
Check <https://en.wikipedia.org/wiki/Coefficient_of_variation>.
92
93
-[](<>)
93
+
web/api/queries/sum/README.md
+1
-1
@@ -38,4 +38,4 @@ Examining last 1 minute `successful` web server responses:
38
39
- <https://en.wikipedia.org/wiki/Summation>.
40
41
-[](<>)
41
+
web/gui/README.md
-2
@@ -165,5 +165,3 @@ file](https://user-images.githubusercontent.com/1153921/62798924-570e6c80-ba94-1
165
166
For information on creating custom dashboards from scratch, see the [custom dashboards](/web/gui/custom/README.md) or
167
[Atlassian Confluence dashboards](/web/gui/confluence/README.md) guides.
168
-
169
-[]()
web/gui/confluence/README.md
+1
-1
@@ -1016,4 +1016,4 @@ NETDATA.options.current.eliminate_zero_dimensions = false;
1016
</div>
1017
```
1018
1019
-[](<>)
1019
+
web/gui/custom/README.md
-1
@@ -602,4 +602,3 @@ to 50.
602
604
605
-[]()
web/server/README.md
+1
-1
@@ -242,4 +242,4 @@ If you publish your Netdata to the internet, you may want to apply some protecti
242
4. Run the `netdata` process with a low process scheduling priority (the default is the lowest)
243
5. If possible, proxy Netdata via a full featured web server (nginx, apache, etc)
244
245
-[](<>)
245
+
web/server/static/README.md
+1
-1
@@ -14,4 +14,4 @@ Each thread uses non-blocking I/O so it can serve any number of web requests in
14
15
This web server respects the `keep-alive` HTTP header to serve multiple HTTP requests via the same connection.
16
17
-[](<>)
17
+