diff options
Diffstat (limited to 'backends/prometheus/README.md')
| -rw-r--r-- | backends/prometheus/README.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/backends/prometheus/README.md b/backends/prometheus/README.md index 99a11f942..8cf83cbf4 100644 --- a/backends/prometheus/README.md +++ b/backends/prometheus/README.md @@ -9,7 +9,7 @@ Prometheus is a distributed monitoring system which offers a very simple setup a ### Installing netdata -There are number of ways to install netdata according to [Installation](../../installer/#installation) +There are number of ways to install netdata according to [Installation](../../packaging/installer/#installation) The suggested way of installing the latest netdata and keep it upgrade automatically. Using one line installation: ``` @@ -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. + +[]() |