summaryrefslogtreecommitdiffstats
path: root/backends/README.md
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2019-11-28 04:53:29 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2019-11-28 04:53:29 +0000
commit17c93e2be4ad7b3af0cd6878bdd5d8a4a3e6da99 (patch)
tree3e0c96613972e8bb4afdeeb97a034806363ddfa9 /backends/README.md
parentReleasing debian version 1.18.1-1. (diff)
downloadnetdata-17c93e2be4ad7b3af0cd6878bdd5d8a4a3e6da99.tar.xz
netdata-17c93e2be4ad7b3af0cd6878bdd5d8a4a3e6da99.zip
Merging upstream version 1.19.0.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'backends/README.md')
-rw-r--r--backends/README.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/backends/README.md b/backends/README.md
index ac0847dca..470544774 100644
--- a/backends/README.md
+++ b/backends/README.md
@@ -39,6 +39,9 @@ So, although Netdata collects metrics every second, it can send to the backend s
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/).
+ - ****TimescaleDB** via [community-built connector](TIMESCALE.md) that takes JSON streams from a Netdata client
+ and writes them to a TimescaleDB table.
+
- **AWS Kinesis Data Streams**
metrics are sent to the service in `JSON` format.