diff options
| author | Chris Akritidis <43294513+cakrit@users.noreply.github.com> | 2018-12-07 11:30:04 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-12-07 11:30:04 +0100 |
| commit | 415f57c5bf6f41421a3bb88d4f250b8fb94376ee (patch) | |
| tree | 34f237f739c42aa0f43db432f8459239aae77702 /backends | |
| parent | 9d7e58cdc4ffc21994ab305951a69d73fc263af7 (diff) | |
Ga (#4938)
* Added GA tags to markdowns
* Add GA tags to mds
Diffstat (limited to 'backends')
| -rw-r--r-- | backends/README.md | 2 | ||||
| -rw-r--r-- | backends/WALKTHROUGH.md | 2 | ||||
| -rw-r--r-- | backends/prometheus/README.md | 2 |
3 files changed, 6 insertions, 0 deletions
diff --git a/backends/README.md b/backends/README.md index 67da7ad71c..39cba873e4 100644 --- a/backends/README.md +++ b/backends/README.md @@ -196,3 +196,5 @@ netdata adds 4 alarms:  + +[]() diff --git a/backends/WALKTHROUGH.md b/backends/WALKTHROUGH.md index b899556ab2..0c24d08c23 100644 --- a/backends/WALKTHROUGH.md +++ b/backends/WALKTHROUGH.md @@ -290,3 +290,5 @@ automatically begins to scrape them. Once achieved you do not have to think about the monitoring system until Prometheus cannot keep up with your scale. Once this happens there are options presented in the Prometheus documentation for solving this. Hope this was helpful, happy monitoring. + +[]() diff --git a/backends/prometheus/README.md b/backends/prometheus/README.md index 99a11f9425..55b424b3c2 100644 --- a/backends/prometheus/README.md +++ b/backends/prometheus/README.md @@ -378,3 +378,5 @@ It can also be changed from the URL, by appending `&prefix=netdata`. When the data source is set to `average` or `sum`, netdata remembers the last access of each client accessing prometheus metrics and uses this last access time to respond with the `average` or `sum` of all the entries in the database since that. This means that prometheus servers are not losing data when they access netdata with data source = `average` or `sum`. To uniquely identify each prometheus server, netdata uses the IP of the client accessing the metrics. If however the IP is not good enough for identifying a single prometheus server (e.g. when prometheus servers are accessing netdata through a web proxy, or when multiple prometheus servers are NATed to a single IP), each prometheus may append `&server=NAME` to the URL. This `NAME` is used by netdata to uniquely identify each prometheus server and keep track of its last access time. + +[]() |