summaryrefslogtreecommitdiffstats
path: root/backends
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2019-08-04 08:56:44 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2019-08-04 08:56:44 +0000
commit34f488f41ee820371159111bf621f11d0f54f669 (patch)
tree13eea1c3aa3d905ec929691bbf23d8b90bef1dcb /backends
parentAdding upstream version 1.16.0. (diff)
downloadnetdata-34f488f41ee820371159111bf621f11d0f54f669.tar.xz
netdata-34f488f41ee820371159111bf621f11d0f54f669.zip
Adding upstream version 1.16.1.upstream/1.16.1
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to '')
-rw-r--r--backends/README.md4
-rw-r--r--backends/opentsdb/README.md13
2 files changed, 9 insertions, 8 deletions
diff --git a/backends/README.md b/backends/README.md
index bdc409017..ef5baa1b6 100644
--- a/backends/README.md
+++ b/backends/README.md
@@ -33,7 +33,9 @@ X seconds (though, it can send them per second if you need it to).
- **prometheus** is described at [prometheus page](prometheus/) since it pulls data from netdata.
- **prometheus remote write** (a binary snappy-compressed protocol buffer encoding over HTTP used by
- a lot of [storage providers](https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage))
+ **Elasticsearch**, **Gnocchi**, **Graphite**, **InfluxDB**, **Kafka**, **OpenTSDB**,
+ **PostgreSQL/TimescaleDB**, **Splunk**, **VictoriaMetrics**,
+ and a lot of other [storage providers](https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage))
metrics are labeled in the format, which is used by Netdata for the [plaintext prometheus protocol](prometheus/).
Notes on using the remote write backend are [here](prometheus/remote_write/).
diff --git a/backends/opentsdb/README.md b/backends/opentsdb/README.md
index 3d57e2e1a..ab1f08bd3 100644
--- a/backends/opentsdb/README.md
+++ b/backends/opentsdb/README.md
@@ -1,7 +1,6 @@
# OpenTSDB with HTTP
-Since version 1.16 the Netdata has the feature to communicate with OpenTSDB using HTTP API. To enable this channel
-it is necessary to set the following options in your netdata.conf
+Netdata can easily communicate with OpenTSDB using HTTP API. To enable this channel, set the following options in your `netdata.conf`:
```
[backend]
@@ -9,13 +8,13 @@ it is necessary to set the following options in your netdata.conf
destination = localhost:4242
```
-, in this example we are considering that OpenTSDB is running with its default port (4242).
+In this example, OpenTSDB is running with its default port, which is `4242`. If you run OpenTSDB on a different port, change the `destination = localhost:4242` line accordingly.
## HTTPS
-Netdata also supports sending the metrics using SSL/TLS, but OpenTDSB does not have support to safety connections,
-so it will be necessary to configure a reverse-proxy to enable the HTTPS communication. After to configure your proxy the
-following changes must be done in the netdata.conf:
+As of [v1.16.0](https://github.com/netdata/netdata/releases/tag/v1.16.0), Netdata can send metrics to OpenTSDB using TLS/SSL. Unfortunately, OpenTDSB does not support encrypted connections, so you will have to configure a reverse proxy to enable HTTPS communication between Netdata and OpenTSBD. You can set up a reverse proxy with [Nginx](../../docs/Running-behind-nginx.md).
+
+After your proxy is configured, make the following changes to `netdata.conf`:
```
[backend]
@@ -23,4 +22,4 @@ following changes must be done in the netdata.conf:
destination = localhost:8082
```
-In this example we used the port 8082 for our reverse proxy.
+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.