opensourcemirror
/
netdata
mirror of https://github.com/netdata/netdata.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Docs housekeeping for SEO and syntax, part 1 (#10388) 

* First pass to get the script working right

* Finish adding analytics tags
This commit is contained in:
Joel Hans 2021-01-07 11:44:43 -07:00 committed by GitHub
parent 0bb7a429b6
commit 46a8075c8f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
151 changed files with 344 additions and 303 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
BREAKING_CHANGES.md
View File

@ -1,10 +1,11 @@
<!--
---
title: "Breaking Changes"
title: "Breaking changes"
description: "On occasion, the Netdata team must make significant changes to the open-source Netdata Agent. We publish those breaking changes here for reference."
custom_edit_url: https://github.com/netdata/netdata/edit/master/BREAKING_CHANGES.md
---
-->
# Breaking Changes
# Breaking changes
- 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)]
[![analytics](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%2BREAKING_CHANGES&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)

3
BUILD.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "The build system"
custom_edit_url: https://github.com/netdata/netdata/edit/master/BUILD.md
---
-->
# The build system
@ -364,3 +362,4 @@ Some smaller miscellaeneous suggestions:
* [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)
* [how to write platform checks](https://gitlab.kitware.com/cmake/community/wikis/doc/tutorials/How-To-Write-Platform-Checks)
[![analytics](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%2FBUILD&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)

2
CODE_OF_CONDUCT.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Netdata Community Code of Conduct"
custom_edit_url: https://github.com/netdata/netdata/edit/master/CODE_OF_CONDUCT.md
---
-->
# Netdata Community Code of Conduct

2
REDISTRIBUTED.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Redistributed software"
custom_edit_url: https://github.com/netdata/netdata/edit/master/REDISTRIBUTED.md
---
-->
# Redistributed software

3
SECURITY.md
View File

@ -1,8 +1,7 @@
<!--
---
title: "Security Policy"
description: "The Netdata team maintains and adheres to a formal process any time a member of the community reports a security vulnerability."
custom_edit_url: https://github.com/netdata/netdata/edit/master/SECURITY.md
---
-->
# Security Policy

2
backends/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Metrics long term archiving"
custom_edit_url: https://github.com/netdata/netdata/edit/master/backends/README.md
---
-->
# Metrics long term archiving

2
backends/TIMESCALE.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Writing metrics to TimescaleDB"
custom_edit_url: https://github.com/netdata/netdata/edit/master/backends/TIMESCALE.md
---
-->
# Writing metrics to TimescaleDB

2
backends/WALKTHROUGH.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Netdata, Prometheus, Grafana stack"
custom_edit_url: https://github.com/netdata/netdata/edit/master/backends/WALKTHROUGH.md
---
-->
# Netdata, Prometheus, Grafana stack

2
backends/aws_kinesis/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Using Netdata with AWS Kinesis Data Streams"
custom_edit_url: https://github.com/netdata/netdata/edit/master/backends/aws_kinesis/README.md
---
-->
# Using Netdata with AWS Kinesis Data Streams

2
backends/mongodb/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "MongoDB backend"
custom_edit_url: https://github.com/netdata/netdata/edit/master/backends/mongodb/README.md
---
-->
# MongoDB backend

4
backends/opentsdb/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "OpenTSDB with HTTP"
custom_edit_url: https://github.com/netdata/netdata/edit/master/backends/opentsdb/README.md
---
-->
# OpenTSDB with HTTP
@ -36,3 +34,5 @@ After your proxy is configured, make the following changes to `netdata.conf`:
In this example, we used the port `8082` for our reverse proxy. If your reverse proxy listens on a different port,
change the `destination = localhost:8082` line accordingly.
[![analytics](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%2Fbackends%2Fopentsdb%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

2
backends/prometheus/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Using Netdata with Prometheus"
custom_edit_url: https://github.com/netdata/netdata/edit/master/backends/prometheus/README.md
---
-->
# Using Netdata with Prometheus

2
backends/prometheus/remote_write/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Prometheus remote write backend"
custom_edit_url: https://github.com/netdata/netdata/edit/master/backends/prometheus/remote_write/README.md
---
-->
# Prometheus remote write backend

3
build_external/README.md
View File

@ -1,9 +1,7 @@
<!--
---
title: "External build-system"
date: 2020-03-31
custom_edit_url: https://github.com/netdata/netdata/edit/master/build_external/README.md
---
-->
# External build-system
@ -127,3 +125,4 @@ Notes:
* There is not yet a good way to configure the target agent container from the docker-compose command line.
* Several other containers should be in this compose (a paho client, tshark etc).
[![analytics](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%2Fbuild_external%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

2
claim/README.md
View File

@ -1,6 +1,6 @@
<!--
title: "Agent claiming"
description: "Agent claiming allows a Netdata Agent, running on a distributed node, to securely connect to Netdata Cloud. A Space's administrator creates a claiming token, which is used to add an Agent to their Space via the Agent-Cloud link."
description: "Agent claiming allows a Netdata Agent, running on a distributed node, to securely connect to Netdata Cloud via the encrypted Agent-Cloud link (ACLK)."
custom_edit_url: https://github.com/netdata/netdata/edit/master/claim/README.md
-->

9
cli/README.md
View File

@ -1,13 +1,12 @@
<!--
---
title: "Netdata cli"
title: "Netdata CLI"
description: "The Netdata Agent includes a command-line experience for reloading health configuration, reopening log files, halting the daemon, and more."
custom_edit_url: https://github.com/netdata/netdata/edit/master/cli/README.md
---
-->
# Netdata cli
# Netdata CLI
You can see the commands netdatacli supports by executing it with `netdatacli` and entering `help` in
You can see the commands `netdatacli` supports by executing it with `netdatacli` and entering `help` in
standard input. All commands are given as standard input to `netdatacli`.
The commands that a running netdata agent can execute are the following:

4
collectors/QUICKSTART.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Collectors quickstart"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/QUICKSTART.md
---
-->
# Collectors quickstart
@ -123,3 +121,5 @@ popular collectors.
Finally, learn more advanced collector features, such as disabling plugins or developing a custom collector, in our
[internal plugin API](/collectors/REFERENCE.md#internal-plugins-api) or our [external plugin
docs](/collectors/plugins.d/README.md).
[![analytics](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%2Fcollectors%2FQUICKSTART&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

2
collectors/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Collecting metrics"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/README.md
---
-->
# Collecting metrics

4
collectors/REFERENCE.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Collectors configuration reference"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/REFERENCE.md
---
-->
# Collectors configuration reference
@ -184,3 +182,5 @@ through this, is to examine what other similar plugins do.
## Write a custom collector
You can add custom collectors by following the [external plugins documentation](../collectors/plugins.d/).
[![analytics](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%2Fcollectors%2REFERENCE&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

2
collectors/cgroups.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "cgroups.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/cgroups.plugin/README.md
---
-->
# cgroups.plugin

2
collectors/checks.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "checks.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/checks.plugin/README.md
---
-->
# checks.plugin

4
collectors/cups.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "cups.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/cups.plugin/README.md
---
-->
# cups.plugin
@ -60,3 +58,5 @@ For each destination the plugin provides these charts:
- processing
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.
[![analytics](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%2Fcollectors%2cups.plugin%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

3
collectors/diskspace.plugin/README.md
View File

@ -1,8 +1,7 @@
<!--
---
title: "diskspace.plugin"
description: "Monitor the disk usage space of mounted disks in real-time with the Netdata Agent, plus preconfigured alarms for disks at risk of filling up."
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/diskspace.plugin/README.md
---
-->
# diskspace.plugin

2
collectors/fping.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "fping.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/fping.plugin/README.md
---
-->
# fping.plugin

2
collectors/freebsd.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "freebsd.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/freebsd.plugin/README.md
---
-->
# freebsd.plugin

2
collectors/freeipmi.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "freeipmi.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/freeipmi.plugin/README.md
---
-->
# freeipmi.plugin

2
collectors/idlejitter.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "idlejitter.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/idlejitter.plugin/README.md
---
-->
# idlejitter.plugin

2
collectors/ioping.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "ioping.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/ioping.plugin/README.md
---
-->
# ioping.plugin

2
collectors/macos.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "macos.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/macos.plugin/README.md
---
-->
# macos.plugin

2
collectors/nfacct.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "nfacct.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/nfacct.plugin/README.md
---
-->
# nfacct.plugin

2
collectors/perf.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "perf.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/perf.plugin/README.md
---
-->
# perf.plugin

2
collectors/plugins.d/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "External plugins overview"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/plugins.d/README.md
---
-->
# External plugins overview

2
collectors/proc.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "proc.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/proc.plugin/README.md
---
-->
# proc.plugin

2
collectors/python.d.plugin/alarms/README.md
View File

@ -54,3 +54,5 @@ local:
```
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`
[![analytics](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%2Fcollectors%2Fpython.d.plugin%2Falarms%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

2
collectors/python.d.plugin/am2320/README.md
View File

@ -50,3 +50,5 @@ Software install:
- save the file.
- restart the netdata service.
- check the dashboard.
[![analytics](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%2Fcollectors%2Fpython.d.plugin%2Fam2320%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

2
collectors/python.d.plugin/anomalies/README.md
View File

@ -225,3 +225,5 @@ If you would like to go deeper on what exactly the anomalies collector is doing
- [Mendeley public group](https://www.mendeley.com/community/interesting-anomaly-detection-papers/) with some interesting anomaly detection papers we have been reading.
- 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.
- Novelty and outlier detection in the [scikit-learn documentation](https://scikit-learn.org/stable/modules/outlier_detection.html).
[![analytics](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%2Fcollectors%2Fpython.d.plugin%2Fanomalies%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

2
collectors/python.d.plugin/gearman/README.md
View File

@ -48,4 +48,4 @@ localhost:
When no configuration file is found, module tries to connect to TCP/IP socket: `localhost:4730`.
---
[![analytics](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%2Fcollectors%2Fpython.d.plugin%2Fgearman%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

2
collectors/python.d.plugin/hpssa/README.md
View File

@ -51,3 +51,5 @@ If `ssacli` cannot be found in the `PATH`, configure it in `hpssa.conf`.
```yaml
ssacli_path: /usr/sbin/ssacli
```
[![analytics](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%2Fcollectors%2Fpython.d.plugin%2Fhpssa%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

2
collectors/python.d.plugin/riakkv/README.md
View File

@ -124,3 +124,5 @@ With no explicit configuration given, the module will attempt to connect to
The default update frequency for the plugin is set to 2 seconds as Riak
internally updates the metrics every second. If we were to update the metrics
every second, the resulting graph would contain odd jitter.
[![analytics](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%2Fcollectors%2Fpython.d.plugin%2Friakkv%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

2
collectors/slabinfo.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "slabinfo.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/slabinfo.plugin/README.md
---
-->
# slabinfo.plugin

21
collectors/statsd.plugin/README.md
View File

@ -1,8 +1,7 @@
<!--
---
title: "statsd.plugin"
description: "The Netdata Agent is a fully-featured statsd server that collects metrics from any custom application and visualizes them in real-time."
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/statsd.plugin/README.md
---
-->
# statsd.plugin
@ -219,7 +218,8 @@ The same chart with the `sum` unselected:
### synthetic statsd charts
Using synthetic charts, you can create dedicated sections on the dashboard to render the charts. You can control everything: the main menu, the submenus, the charts, the dimensions on each chart, etc.
Use synthetic charts to create dedicated sections on the dashboard to render the charts, with control over the main
menu, the submenus, the charts, the dimensions on each chart, and more.
Synthetic charts are organized in
@ -229,7 +229,7 @@ Synthetic charts are organized in
For each application you need to create a `.conf` file in `/etc/netdata/statsd.d`.
So, to create the statsd application `myapp`, you can create the file `/etc/netdata/statsd.d/myapp.conf`, with this content:
So, to create the statsd application `myapp`, create the file `/etc/netdata/statsd.d/myapp.conf`, with this content:
```
[app]
@ -271,9 +271,9 @@ Using the above configuration `myapp` should get its own section on the dashboar
`[dictionary]` defines name-value associations. These are used to renaming metrics, when added to synthetic charts. Metric names are also defined at each `dimension` line. However, using the dictionary dimension names can be declared globally, for each app and is the only way to rename dimensions when using patterns. Of course the dictionary can be empty or missing.
Then, you can add any number of charts. Each chart should start with `[id]`. The chart will be called `app_name.id`. `family` controls the submenu on the dashboard. `context` controls the alarm templates. `priority` controls the ordering of the charts on the dashboard. The rest of the settings are informational.
Then, add any number of charts. Each chart should start with `[id]`. The chart will be called `app_name.id`. `family` controls the submenu on the dashboard. `context` controls the alarm templates. `priority` controls the ordering of the charts on the dashboard. The rest of the settings are informational.
You can add any number of metrics to a chart, using `dimension` lines. These lines accept 5 space separated parameters:
Add any number of metrics to a chart, using `dimension` lines. These lines accept 5 space separated parameters:
1. the metric name, as it is collected (it has to be matched by the `metrics =` pattern of the app)
2. the dimension name, as it should be shown on the chart
@ -351,12 +351,12 @@ Netdata uses this dictionary as follows:
3. If any of the above succeeds, Netdata uses the `value` of the dictionary, to set the name of the dimension. The dimensions will have as ID the original statsd metric name, and as name, the dictionary value.
So, you can use the dictionary in 2 ways:
Use the dictionary in 2 ways:
1. set `dimension = myapp.metric1 ''` and have at the dictionary `myapp.metric1 = metric1 name`
2. set `dimension = myapp.metric1 'm1'` and have at the dictionary `m1 = metric1 name`
In both cases, the dimension will be added with ID `myapp.metric1` and will be named `metric1 name`. So, in alarms you can use either of the 2 as `${myapp.metric1}` or `${metric1 name}`.
In both cases, the dimension will be added with ID `myapp.metric1` and will be named `metric1 name`. So, in alarms use either of the 2 as `${myapp.metric1}` or `${metric1 name}`.
> keep in mind that if you add multiple times the same statsd metric to a chart, Netdata will append `TYPE` to the dimension ID, so `myapp.metric1` will be added as `myapp.metric1_last` or `myapp.metric1_events`, etc. If you add multiple times the same metric with the same `TYPE` to a chart, Netdata will also append an incremental counter to the dimension ID, i.e. `myapp.metric1_last1`, `myapp.metric1_last2`, etc.
@ -389,7 +389,7 @@ To add all response codes of `myapp.api.get` to a chart use this:
dimension = pattern 'myapp.api.get.* '' last 1 1
```
The above will add dimension named `200`, `400` and `500` (yes, Netdata extracts the wildcarded part of the metric name - so the dimensions will be named with whatever the `*` matched). You can rename the dimensions with this:
The above will add dimension named `200`, `400` and `500` (yes, Netdata extracts the wildcarded part of the metric name - so the dimensions will be named with whatever the `*` matched). Rename the dimensions with this:
```
[dictionary]
@ -451,7 +451,8 @@ Using the above, the dimensions will be added as `GET`, `ADD` and `DELETE`.
## sending statsd metrics from shell scripts
You can send/update statsd metrics from shell scripts. You can use this feature, to visualize in Netdata automated jobs you run on your servers.
Send/update statsd metrics from shell scripts to visualize automated jobs you run on your servers using the Netdata
Agent.
The command you need to run is:

2
collectors/tc.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "tc.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/tc.plugin/README.md
---
-->
# tc.plugin

2
collectors/xenstat.plugin/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "xenstat.plugin"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/xenstat.plugin/README.md
---
-->
# xenstat.plugin

2
contrib/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Netdata contrib"
custom_edit_url: https://github.com/netdata/netdata/edit/master/contrib/README.md
---
-->
# Netdata contrib

2
contrib/sles11/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Spec to build Netdata RPM for sles 11"
custom_edit_url: https://github.com/netdata/netdata/edit/master/contrib/sles11/README.md
---
-->
# Spec to build Netdata RPM for sles 11

2
daemon/README.md
View File

@ -1,9 +1,7 @@
<!--
---
title: "Netdata daemon"
date: 2020-04-29
custom_edit_url: https://github.com/netdata/netdata/edit/master/daemon/README.md
---
-->
# Netdata daemon

4
daemon/config/README.md
View File

@ -1,9 +1,7 @@
<!--
---
title: "Daemon configuration"
date: 2020-03-31
description: "The Netdata Agent's daemon is installed preconfigured to collect thousands of metrics every second, but is highly configurable for real-world workloads."
custom_edit_url: https://github.com/netdata/netdata/edit/master/daemon/config/README.md
---
-->
# Daemon configuration

3
database/README.md
View File

@ -1,8 +1,7 @@
<!--
---
title: "Database"
description: "The Netdata Agent leverages multiple, user-configurable time-series databases that use RAM and/or disk to store metrics on any type of node."
custom_edit_url: https://github.com/netdata/netdata/edit/master/database/README.md
---
-->
# Database

2
diagrams/data_structures/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Data structures"
custom_edit_url: https://github.com/netdata/netdata/edit/master/diagrams/data_structures/README.md
---
-->
# Data structures

4
docs/Add-more-charts-to-netdata.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Add more charts to Netdata"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/Add-more-charts-to-netdata.md
---
-->
# Add more charts to Netdata
@ -14,3 +12,5 @@ guide](/collectors/QUICKSTART.md) for more information.
See the [list of supported collectors](/collectors/COLLECTORS.md) to see all the sources Netdata can collect metrics
from.
[![analytics](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%2Fdocs%2FAdd-more-charts-to-netdata&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

2
docs/Demo-Sites.md
View File

@ -1,9 +1,7 @@
<!--
---
title: "Demo sites"
date: 2020-03-26
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/Demo-Sites.md
---
-->
# Demo sites

2
docs/Donations-netdata-has-received.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Donations"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/Donations-netdata-has-received.md
---
-->
# Donations

4
docs/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Read documentation on <https://learn.netdata.cloud>"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/README.md
---
-->
# Read documentation on <https://learn.netdata.cloud>
@ -15,3 +13,5 @@ uses a few extra Markdown features that GitHub doesn't support natively. Other t
perfect.
Now get out there and build an exceptional infrastructure.
[![analytics](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%2Fdocs%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)

2
docs/Running-behind-apache.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Netdata via apache's mod_proxy"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/Running-behind-apache.md
---
-->
# Netdata via apache's mod_proxy

2
docs/Running-behind-caddy.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Netdata via Caddy"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/Running-behind-caddy.md
---
-->
# Netdata via Caddy

2
docs/Running-behind-haproxy.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Netdata via HAProxy"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/Running-behind-haproxy.md
---
-->
# Netdata via HAProxy

2
docs/Running-behind-lighttpd.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Netdata via lighttpd v1.4.x"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/Running-behind-lighttpd.md
---
-->
# Netdata via lighttpd v1.4.x

2
docs/Running-behind-nginx.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Running Netdata behind Nginx"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/Running-behind-nginx.md
---
-->
# Running Netdata behind Nginx

2
docs/a-github-star-is-important.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "A GitHub star is important"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/a-github-star-is-important.md
---
-->
# A GitHub star is important

6
docs/agent-cloud.md
View File

@ -1,9 +1,7 @@
<!--
---
title: "Use the Agent with Netdata Cloud"
date: 2020-05-04
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/agent-cloud.md
---
-->
# Use the Agent with Netdata Cloud
@ -76,4 +74,6 @@ about how you might want to use or configure Cloud, we recommend the following:
- Follow the 5-minute [get started with Cloud](https://learn.netdata.cloud/docs/cloud/get-started/) guide to finish
onboarding and claim your first nodes.
- Better understand how agents connect securely to the Cloud with [claiming](/claim/README.md) and [Agent-Cloud
link](/aclk/README.md) documentation.
link](/aclk/README.md) documentation.
[![analytics](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%2Fdocs%2Fagent-cloud&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

5
docs/anonymous-statistics.md
View File

@ -1,8 +1,7 @@
<!--
---
title: "Anonymous statistics"
description: "The Netdata Agent collects anonymous usage information by default and sends it to Google Analytics for quality assurance and product decisions."
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/anonymous-statistics.md
---
-->
# Anonymous statistics
@ -106,3 +105,5 @@ Each of these opt-out processes does the following:
- Forces the anonymous statistics script to exit immediately.
- Stops the Google Tag Manager Javascript snippet, which remains on the dashboard, from firing and sending any data to
Google Analytics.
[![analytics](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%2Fdocs%2Fanonymous-statistics&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

211
docs/configuration-guide.md Normal file
View File

@ -0,0 +1,211 @@
<!--
title: "Configuration guide"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/configuration-guide.md
-->
# Configuration guide
No configuration is required to run Netdata, but you will find plenty of options to tweak, so that you can adapt it to
your particular needs.
<details markdown="1"><summary>Configuration files are placed in `/etc/netdata`.</summary>
Depending on your installation method, Netdata will have been installed either directly under `/`, or under `/opt/netdata`. The paths mentioned here and in the documentation in general assume that your installation is under `/`. If it is not, you will find the exact same paths under `/opt/netdata` as well. (i.e. `/etc/netdata` will be `/opt/netdata/etc/netdata`).</details>
Under that directory you will see the following:
- `netdata.conf` is [the main configuration file](/daemon/config/README.md#daemon-configuration)
- `edit-config` is an sh script that you can use to easily and safely edit the configuration. Just run it to see its
usage.
- Other directories, initially empty, where your custom configurations for alarms and collector plugins/modules will
be copied from the stock configuration, if and when you customize them using `edit-config`.
- `orig` is a symbolic link to the directory `/usr/lib/netdata/conf.d`, which contains the stock configurations for
everything not included in `netdata.conf`:
- `health_alarm_notify.conf` is where you configure how and to who Netdata will send [alarm
notifications](/health/notifications/README.md#netdata-alarm-notifications).
- `health.d` is the directory that contains the alarm triggers for [health
monitoring](/health/README.md#health-monitoring). It contains one .conf file per collector.
- The [modular plugin orchestrators](/collectors/plugins.d/README.md#external-plugins-overview) have:
- One config file each, mainly to turn their modules on and off: `python.d.conf` for
[python](/collectors/python.d.plugin/README.md#pythondplugin), `node.d.conf` for
[nodejs](/collectors/node.d.plugin/README.md#nodedplugin) and `charts.d.conf` for
[bash](/collectors/charts.d.plugin/README.md#chartsdplugin) modules.
- One directory each, where the module-specific configuration files can be found.
- `stream.conf` is where you configure [streaming and
replication](/streaming/README.md#streaming-and-replication)
- `stats.d` is a directory under which you can add .conf files to add [synthetic
charts](/collectors/statsd.plugin/README.md#synthetic-statsd-charts).
- Individual collector plugin config files, such as `fping.conf` for the [fping
plugin](/collectors/fping.plugin/) and `apps_groups.conf` for the [apps plugin](/collectors/apps.plugin/)
So there are many configuration files to control every aspect of Netdata's behavior. It can be overwhelming at first,
but you won't have to deal with any of them, unless you have specific things you need to change. The following HOWTO
will guide you on how to customize your Netdata, based on what you want to do.
## How to
### Persist my configuration
In `http://localhost:19999/netdata.conf`, you will see the following two parameters:
```bash
# config directory = /etc/netdata
# stock config directory = /usr/lib/netdata/conf.d
```
To persist your configurations, don't edit the files under the `stock config directory` directly. Use the `sudo [config
directory]/edit-config` command, or copy the stock config file to its proper place under the `config directory` and edit
it there.
### Change what I see
#### Increase the long-term metrics retention period
Increase the values for the `page cache size` and `dbengine disk space` settings in the [`[global]`
section](/daemon/config/README.md#global-section-options) of `netdata.conf`. Read our guide on [increasing
long-term metrics storage](/docs/guides/longer-metrics-storage.md) and the [memory requirements for the database
engine](/database/engine/README.md#memory-requirements).
#### Reduce the data collection frequency
Increase `update every` in [netdata.conf \[global\]](/daemon/config/README.md#global-section-options). This is another
way to increase your metrics retention period, but at a lower resolution than the default 1s.
#### Modify how a chart is displayed
In `netdata.conf` under `# Per chart configuration` you will find several [\[CHART_NAME\]
sections](/daemon/config/README.md#per-chart-configuration), where you can control all aspects of a specific chart.
#### Disable a collector
Entire plugins can be turned off from the [netdata.conf \[plugins\]](/daemon/config/README.md#plugins-section-options)
section. To disable specific modules of a plugin orchestrator, you need to edit one of the following:
- `python.d.conf` for [python](/collectors/python.d.plugin/README.md)
- `node.d.conf` for [nodejs](/collectors/node.d.plugin/README.md)
- `charts.d.conf` for [bash](/collectors/charts.d.plugin/README.md)
#### Show charts with zero metrics
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.
### Modify alarms and notifications
#### Add a new alarm
You can add a new alarm definition either by editing an existing stock alarm config file under `health.d` (e.g.
`/etc/netdata/edit-config health.d/load.conf`), or by adding a new `.conf` file under `/etc/netdata/health.d`. The
documentation on how to define an alarm is in [health monitoring](/health/README.md). It is
suggested to look at some of the stock alarm definitions, so you can ensure you understand how the various options work.
#### Turn off all alarms and notifications
Just set `enabled = no` in the [netdata.conf \[health\]](/daemon/config/README.md#health-section-options) section
#### Modify or disable a specific alarm
The `health.d` directory that contains the alarm triggers for [health monitoring](/health/README.md). It has
one .conf file per collector. You can easily find the .conf file you will need to modify, by looking for the "source"
line on the table that appears on the right side of an alarm on the Netdata gui.
For example, if you click on Alarms and go to the tab 'All', the default Netdata installation will show you at the top
the configured alarm for `10 min cpu usage` (it's the name of the badge). Looking at the table on the right side, you
will see a row that says: `source 4@/usr/lib/netdata/conf.d/health.d/cpu.conf`. This way, you know that you will need
to run `/etc/netdata/edit-config health.d/cpu.conf` and look for alarm at line 4 of the conf file.
As stated at the top of the .conf file, **you can disable an alarm notification by setting the 'to' line to: silent**.
To modify how the alarm gets triggered, we suggest that you go through the guide on [health
monitoring](/health/README.md#health-monitoring).
#### Receive notifications using my preferred method
You only need to configure `health_alarm_notify.conf`. To learn how to do it, read first [alarm
notifications](/health/notifications/README.md#netdata-alarm-notifications) and then open the submenu `Supported
Notifications` under `Alarm notifications` in the documentation to find the specific page on your preferred notification
method.
### Make security-related customizations
#### Change the Netdata web server access lists
You have several options under the [netdata.conf \[web\]](/web/server/README.md#access-lists) section.
#### Stop sending info to registry.my-netdata.io
You will need to configure the `[registry]` section in `netdata.conf`. First read the [registry
documentation](/registry/). In it, are instructions on how to [run your own
registry](/registry/README.md#run-your-own-registry).
#### Change the IP address/port Netdata listens to
The settings are under the `[web]` section. Look at the [web server
documentation](/web/server/README.md#binding-netdata-to-multiple-ports) for more info.
### System resource usage
#### Reduce the resources Netdata uses
The [Netdata performance guide](/docs/guides/configure/performance.md) outlines many ways to reduce the Netdata
CPU/disk/RAM utilization to levels suitable even for the weakest [IoT devices](/docs/netdata-for-IoT.md).
#### Change when Netdata saves metrics to disk
[netdata.conf \[global\]](/daemon/config/README.md#global-section-options): `memory mode`
#### Prevent Netdata from getting immediately killed when my server runs out of memory
You can change the Netdata [OOM score](/daemon/README.md#oom-score) in `[global]`.
### Other
#### Move Netdata directories
The various directory paths are in [netdata.conf \[global\]](/daemon/config/README.md#global-section-options).
## How Netdata configuration works
The configuration files are `name = value` dictionaries with `[sections]`. Write whatever you like there as long as it
follows this simple format.
Netdata loads this dictionary and then when the code needs a value from it, it just looks up the `name` in the
dictionary at the proper `section`. In all places, in the code, there are both the `names` and their `default values`,
so if something is not found in the configuration file, the default is used. The lookup is made using B-Trees and hashes
(no string comparisons), so they are super fast. Also the `names` of the settings can be `my super duper setting that
once set to yes, will turn the world upside down = no` - so goodbye to most of the documentation involved.
Next, Netdata can generate a valid configuration for the user to edit. No need to remember anything. Just get the
configuration from the server (`/netdata.conf` on your Netdata server), edit it and save it.
Last, what about options you believe you have set, but you misspelled?When you get the configuration file from the
server, there will be a comment above all `name = value` pairs the server does not use. So you know that whatever you
wrote there, is not used.
## Netdata simple patterns
Unix prefers regular expressions. But they are just too hard, too cryptic to use, write and understand.
So, Netdata supports [simple patterns](/libnetdata/simple_pattern/README.md).
## Netdata labels
Beginning with 1.20, Netdata accepts user-defined **host labels**. These labels are defined in the section `[host
labels]`.
Read more about how these labels work and why they're an effective way to organize complex infrasturctures in our
guide: [Use host labels to organize systems, metrics, and alarms](/docs/guides/using-host-labels.md).
To define a label inside this section, some rules needs to be followed, or Netdata will reject the label. The following
restrictions are applied for label names:
- Names cannot start with `_`, but it can be present in other parts of the name.
- Names only accept alphabet letters, numbers, dots, and dashes.
The policy for values is more flexible, but you can not use exclamation marks (`!`), whitespaces (` `), single quotes
(`'`), double quotes (`"`), or asterisks (`*`), because they are used to compare label values in health alarms and
templates.
[![analytics](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%2Fdocs%2Fconfiguration-guide&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)

2
docs/getting-started.md
View File

@ -1,9 +1,7 @@
<!--
---
title: "Get started guide"
date: 2020-05-04
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/getting-started.md
---
-->
# Get started guide

2
docs/guides/deploy/ansible.md
View File

@ -1,6 +1,6 @@
<!--
title: Deploy Netdata with Ansible
description: Deploy an infrastructure monitoring solution in minutes with the Netdata Agent and Ansible. Use and customize a simple playbook for monitoring as code.
description: "Deploy an infrastructure monitoring solution in minutes with the Netdata Agent and Ansible. Use and customize a simple playbook for monitoring as code."
image: /img/seo/guides/deploy/ansible.png
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/guides/deploy/ansible.md
-->

2
docs/guides/export/export-netdata-metrics-graphite.md
View File

@ -1,6 +1,6 @@
<!--
title: Export and visualize Netdata metrics in Graphite
description: Use Netdata to collect and export thousands of metrics to Graphite for long-term storage or further analysis.
description: "Use Netdata to collect and export thousands of metrics to Graphite for long-term storage or further analysis."
image: /img/seo/guides/export/export-netdata-metrics-graphite.png
-->

2
docs/guides/monitor/dimension-templates.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Use dimension templates to create dynamic alarms"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/monitor/health/dimension-templates.md
---
-->
# Use dimension templates to create dynamic alarms

2
docs/guides/monitor/stop-notifications-alarms.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Stop notifications for individual alarms"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/guides/monitor/stop-notifications-alarms.md
---
-->
# Stop notifications for individual alarms

2
docs/netdata-for-IoT.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Netdata for IoT"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/netdata-for-IoT.md
---
-->
# Netdata for IoT

2
docs/netdata-security.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Security design"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/netdata-security.md
---
-->
# Security design

2
docs/privacy-policy.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Privacy Policy"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/privacy-policy.md
---
-->
# Privacy Policy

2
docs/terms-of-use.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Terms of Use"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/terms-of-use.md
---
-->
# Terms of Use

2
docs/why-netdata/1s-granularity.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "1s granularity"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/why-netdata/1s-granularity.md
---
-->
# 1s granularity

2
docs/why-netdata/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Why Netdata"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/why-netdata/README.md
---
-->
# Why Netdata

2
docs/why-netdata/immediate-results.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Immediate results"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/why-netdata/immediate-results.md
---
-->
# Immediate results

2
docs/why-netdata/meaningful-presentation.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Meaningful presentation"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/why-netdata/meaningful-presentation.md
---
-->
# Meaningful presentation

2
docs/why-netdata/unlimited-metrics.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Unlimited metrics"
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/why-netdata/unlimited-metrics.md
---
-->
# Unlimited metrics

3
health/notifications/alerta/README.md
View File

@ -1,8 +1,7 @@
<!--
---
title: "alerta.io"
description: "Send alarm notifications to Alerta to see the latest health status updates from multiple nodes in a single interface."
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/alerta/README.md
---
-->
# alerta.io

3
health/notifications/awssns/README.md
View File

@ -1,8 +1,7 @@
<!--
---
title: "Amazon SNS"
description: "hello"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/awssns/README.md
---
-->
# Amazon SNS

2
health/notifications/custom/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Custom"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/custom/README.md
---
-->
# Custom

2
health/notifications/discord/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Discordapp.com"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/discord/README.md
---
-->
# Discordapp.com

2
health/notifications/dynatrace/README.md
View File

@ -32,3 +32,5 @@ The default value is `CUSTOM_INFO`.
This is a required parameter.
6. Specify the annotation type. This is the source of the Dynatrace event. Put whatever it fits you, for example,
_Netdata Alarm_, which is also the default value.
[![analytics](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%2Fhealth%2Fnotifications%2Fdynatrace%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

2
health/notifications/email/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Email"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/email/README.md
---
-->
# Email

2
health/notifications/irc/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "IRC"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/irc/README.md
---
-->
# IRC

2
health/notifications/kavenegar/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Kavenegar"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/kavenegar/README.md
---
-->
# Kavenegar

2
health/notifications/messagebird/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Messagebird"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/messagebird/README.md
---
-->
# Messagebird

2
health/notifications/pagerduty/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "PagerDuty"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/pagerduty/README.md
---
-->
# PagerDuty

2
health/notifications/prowl/README.md
View File

@ -25,3 +25,5 @@ the Prowl website after registering.
Once you have an API key, simply specify that as a recipient for Prowl
notifications.
[![analytics](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%2Fhealth%2Fnotifications%2Fprowl%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()

2
health/notifications/pushbullet/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "PushBullet"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/pushbullet/README.md
---
-->
# PushBullet

2
health/notifications/pushover/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "PushOver"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/pushover/README.md
---
-->
# PushOver

2
health/notifications/rocketchat/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Rocket.Chat"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/rocketchat/README.md
---
-->
# Rocket.Chat

2
health/notifications/slack/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Slack"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/slack/README.md
---
-->
# Slack

2
health/notifications/smstools3/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "SMS Server Tools 3"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/smstools3/README.md
---
-->
# SMS Server Tools 3

2
health/notifications/syslog/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Syslog"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/syslog/README.md
---
-->
# Syslog

2
health/notifications/telegram/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Telegram"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/telegram/README.md
---
-->
# Telegram

2
health/notifications/twilio/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Twilio"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/twilio/README.md
---
-->
# Twilio

2
health/notifications/web/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Dashboard"
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notifications/web/README.md
---
-->
# Dashboard

2
libnetdata/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "libnetdata"
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/README.md
---
-->
# libnetdata

2
libnetdata/adaptive_resortable_list/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "Adaptive Re-sortable List (ARL)"
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/adaptive_resortable_list/README.md
---
-->
# Adaptive Re-sortable List (ARL)

2
libnetdata/avl/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "AVL"
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/avl/README.md
---
-->
# AVL

2
libnetdata/buffer/README.md
View File

@ -1,8 +1,6 @@
<!--
---
title: "BUFFER"
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/buffer/README.md
---
-->
# BUFFER

Some files were not shown because too many files have changed in this diff Show More