Adding upstream version 1.29.0.upstream/1.29.0

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

2 files changed, 183 insertions, 0 deletions

diff --git a/docs/export/enable-connector.md b/docs/export/enable-connector.md
new file mode 100644
index 00000000..9789de2d
--- /dev/null
+++ b/docs/export/enable-connector.md
@@ -0,0 +1,93 @@
+<!--
+title: "Enable an exporting connector"
+description: "Learn how to enable and configure any connector using examples to start exporting metrics to external time-series databases in minutes."
+custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/export/enable-connector.md
+-->
+
+# Enable an exporting connector
+
+Now that you found the right connector for your [external time-series
+database](/docs/export/external-databases.md#supported-databases), you can now enable the exporting engine and the
+connector itself. We'll walk through the process of enabling the exporting engine itself, followed by two examples using
+the OpenTSDB and Graphite connectors.
+
+> When you enable the exporting engine and a connector, the Netdata Agent exports metrics _beginning from the time you
+> restart its process_, not the entire [database of long-term metrics](/docs/store/change-metrics-storage.md).
+
+Once you understand the process of enabling a connector, you can translate that knowledge to any other connector.
+
+## Enable the exporting engine
+
+Use `edit-config` from your [Netdata config directory](/docs/configure/nodes.md#the-netdata-config-directory) to open
+`exporting.conf`:
+
+```bash
+sudo ./edit-config exporting.conf
+```
+
+Enable the exporting engine itself by setting `enabled` to `yes`:
+
+```conf
+[exporting:global]
+    enabled = yes
+```
+
+Save the file but keep it open, as you will edit it again to enable specific connectors.
+
+## Example: Enable the OpenTSDB connector
+
+Use the following configuration as a starting point. Copy and paste it into `exporting.conf`.
+
+```conf
+[opentsdb:http:my_opentsdb_http_instance]
+    enabled = yes
+    destination = localhost:4242
+```
+
+Replace `my_opentsdb_http_instance` with an instance name of your choice, and change the `destination` setting to the IP
+address or hostname of your OpenTSDB database.
+
+Restart your Agent with `sudo systemctl restart netdata` to begin exporting to your OpenTSDB database. The Netdata Agent
+exports metrics _beginning from the time the process starts_, and because it exports as metrics are collected, you
+should start seeing data in your external database after only a few seconds.
+
+Any further configuration is optional, based on your needs and the configuration of your OpenTSDB database. See the
+[OpenTSDB connector doc](/exporting/opentsdb/README.md) and [exporting engine
+reference](/exporting/README.md#configuration) for details.
+
+## Example: Enable the Graphite connector
+
+Use the following configuration as a starting point. Copy and paste it into `exporting.conf`.
+
+```conf
+[graphite:my_graphite_instance]
+    enabled = yes
+    destination = 203.0.113.0:2003
+```
+
+Replace `my_graphite_instance` with an instance name of your choice, and change the `destination` setting to the IP
+address or hostname of your Graphite-supported database.
+
+Restart your Agent with `sudo systemctl restart netdata` to begin exporting to your Graphite-supported database. Because
+the Agent exports metrics as they're collected, you should start seeing data in your external database after only a few
+seconds.
+
+Any further configuration is optional, based on your needs and the configuration of your Graphite-supported database.
+See [exporting engine reference](/exporting/README.md#configuration) for details.
+
+## What's next?
+
+If you want to further configure your exporting connectors, see the [exporting engine
+reference](/exporting/README.md#configuration).
+
+For a comprehensive example of using the Graphite connector, read our guide: [_Export and visualize Netdata metrics in
+Graphite_](/docs/guides/export/export-netdata-metrics-graphite.md). Or, start [using host
+labels](/docs/guides/using-host-labels.md) on exported metrics.
+
+### Related reference documentation
+
+-   [Exporting engine reference](/exporting/README.md)
+-   [OpenTSDB connector](/exporting/opentsdb/README.md)
+-   [Graphite connector](/exporting/graphite/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%2Fdocs%2Fexporting%2Fenable-connector&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)
diff --git a/docs/export/external-databases.md b/docs/export/external-databases.md
new file mode 100644
index 00000000..309b03a8
--- /dev/null
+++ b/docs/export/external-databases.md
@@ -0,0 +1,90 @@
+<!--
+title: "Export metrics to external time-series databases"
+description: "Use the exporting engine to send Netdata metrics to popular external time series databases for long-term storage or further analysis."
+custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/export/external-databases.md
+-->
+
+# Export metrics to external time-series databases
+
+Netdata allows you to export metrics to external time-series databases with the [exporting
+engine](/exporting/README.md). This system uses a number of **connectors** to initiate connections to [more than
+thirty](#supported-databases) supported databases, including InfluxDB, Prometheus, Graphite, ElasticSearch, and much
+more. 
+
+The exporting engine resamples Netdata's thousands of per-second metrics at a user-configurable interval, and can export
+metrics to multiple time-series databases simultaneously.
+
+Based on your needs and resources you allocated to your external time-series database, you can configure the interval
+that metrics are exported or export only certain charts with filtering. You can also choose whether metrics are exported
+as-collected, a normalized average, or the sum/volume of metrics values over the configured interval.
+
+Exporting is an important part of Netdata's effort to be [interoperable](/docs/overview/netdata-monitoring-stack.md)
+with other monitoring software. You can use an external time-series database for long-term metrics retention, further
+analysis, or correlation with other tools, such as application tracing.
+
+## Supported databases
+
+Netdata supports exporting metrics to the following databases through several
+[connectors](/exporting/README.md#features). Once you find the connector that works for your database, open its
+documentation and the [enabling a connector](/docs/export/enable-connector.md) doc for details on enabling it.
+
+-   **AppOptics**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **AWS Kinesis**: [AWS Kinesis Data Streams](/exporting/aws_kinesis/README.md)
+-   **Azure Data Explorer**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **Azure Event Hubs**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **Blueflood**: [Graphite](/exporting/graphite/README.md)
+-   **Chronix**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **Cortex**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **CrateDB**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **ElasticSearch**: [Graphite](/exporting/graphite/README.md), [Prometheus remote
+    write](/exporting/prometheus/remote_write/README.md)
+-   **Gnocchi**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **Google BigQuery**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **Google Cloud Pub/Sub**: [Google Cloud Pub/Sub Service](/exporting/pubsub/README.md)
+-   **Graphite**: [Graphite](/exporting/graphite/README.md), [Prometheus remote
+    write](/exporting/prometheus/remote_write/README.md)
+-   **InfluxDB**: [Graphite](/exporting/graphite/README.md), [Prometheus remote
+    write](/exporting/prometheus/remote_write/README.md)
+-   **IRONdb**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **JSON**: [JSON document databases](/exporting/json/README.md)
+-   **Kafka**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **KairosDB**: [Graphite](/exporting/graphite/README.md), [OpenTSDB](/exporting/opentsdb/README.md)
+-   **M3DB**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **MetricFire**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **MongoDB**: [MongoDB](/exporting/mongodb/)
+-   **New Relic**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **OpenTSDB**: [OpenTSDB](/exporting/opentsdb/README.md), [Prometheus remote
+    write](/exporting/prometheus/remote_write/README.md)
+-   **PostgreSQL**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+    via [PostgreSQL Prometheus Adapter](https://github.com/CrunchyData/postgresql-prometheus-adapter)
+-   **Prometheus**: [Prometheus scraper](/exporting/prometheus/README.md)
+-   **TimescaleDB**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md),
+    [netdata-timescale-relay](/exporting/TIMESCALE.md)
+-   **QuasarDB**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **SignalFx**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **Splunk**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **TiKV**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **Thanos**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **VictoriaMetrics**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+-   **Wavefront**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md)
+
+Can't find your preferred external time-series database? Ask our [community](https://community.netdata.cloud/) for
+solutions, or file an [issue on
+GitHub](https://github.com/netdata/netdata/issues/new?labels=bug%2C+needs+triage&template=bug_report.md).
+
+## What's next?
+
+We recommend you read our document on [enabling a connector](/docs/export/enable-connector.md) to learn about the
+process and discover important configuration options. If you would rather skip ahead, click on any of the above links to
+connectors for their reference documentation, which outline any prerequisites to install for that connector, along with
+connector-specific configuration options.
+
+Read about one possible use case for exporting metrics in our guide: [_Export and visualize Netdata metrics in
+Graphite_](/docs/guides/export/export-netdata-metrics-graphite.md).
+
+### Related reference documentation
+
+-   [Exporting engine reference](/exporting/README.md)
+-   [Backends reference (deprecated)](/backends/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%2Fdocs%2Fexporting%2Fexternal-databases&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)