summaryrefslogtreecommitdiffstats
path: root/docs/exporting-metrics
diff options
context:
space:
mode:
Diffstat (limited to 'docs/exporting-metrics')
-rw-r--r--docs/exporting-metrics/README.md67
-rw-r--r--docs/exporting-metrics/enable-an-exporting-connector.md43
2 files changed, 110 insertions, 0 deletions
diff --git a/docs/exporting-metrics/README.md b/docs/exporting-metrics/README.md
new file mode 100644
index 000000000..d667cea15
--- /dev/null
+++ b/docs/exporting-metrics/README.md
@@ -0,0 +1,67 @@
+# Export metrics to external time-series databases
+
+Netdata allows you to export metrics to external time-series databases with the [exporting
+engine](/src/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
+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](/src/exporting/README.md#features). Once you find the connector that works for your database, open its
+documentation and the [enabling a connector](/docs/exporting-metrics/enable-an-exporting-connector.md) doc for details on enabling it.
+
+- **AppOptics**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **AWS Kinesis**: [AWS Kinesis Data Streams](/src/exporting/aws_kinesis/README.md)
+- **Azure Data Explorer**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **Azure Event Hubs**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **Blueflood**: [Graphite](/src/exporting/graphite/README.md)
+- **Chronix**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **Cortex**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **CrateDB**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **ElasticSearch**: [Graphite](/src/exporting/graphite/README.md), [Prometheus remote
+ write](/src/exporting/prometheus/remote_write/README.md)
+- **Gnocchi**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **Google BigQuery**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **Google Cloud Pub/Sub**: [Google Cloud Pub/Sub Service](/src/exporting/pubsub/README.md)
+- **Graphite**: [Graphite](/src/exporting/graphite/README.md), [Prometheus remote
+ write](/src/exporting/prometheus/remote_write/README.md)
+- **InfluxDB**: [Graphite](/src/exporting/graphite/README.md), [Prometheus remote
+ write](/src/exporting/prometheus/remote_write/README.md)
+- **IRONdb**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **JSON**: [JSON document databases](/src/exporting/json/README.md)
+- **Kafka**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **KairosDB**: [Graphite](/src/exporting/graphite/README.md), [OpenTSDB](/src/exporting/opentsdb/README.md)
+- **M3DB**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **MetricFire**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **MongoDB**: [MongoDB](/src/exporting/mongodb/README.md)
+- **New Relic**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **OpenTSDB**: [OpenTSDB](/src/exporting/opentsdb/README.md), [Prometheus remote
+ write](/src/exporting/prometheus/remote_write/README.md)
+- **PostgreSQL**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+ via [PostgreSQL Prometheus Adapter](https://github.com/CrunchyData/postgresql-prometheus-adapter)
+- **Prometheus**: [Prometheus scraper](/src/exporting/prometheus/README.md)
+- **TimescaleDB**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md),
+ [netdata-timescale-relay](/src/exporting/TIMESCALE.md)
+- **QuasarDB**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **SignalFx**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **Splunk**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **TiKV**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **Thanos**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **VictoriaMetrics**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
+- **Wavefront**: [Prometheus remote write](/src/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?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml).
diff --git a/docs/exporting-metrics/enable-an-exporting-connector.md b/docs/exporting-metrics/enable-an-exporting-connector.md
new file mode 100644
index 000000000..6a5542fdb
--- /dev/null
+++ b/docs/exporting-metrics/enable-an-exporting-connector.md
@@ -0,0 +1,43 @@
+# Enable an exporting connector
+
+Now that you found the right connector for your [external time-series
+database](/docs/exporting-metrics/README.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.
+
+> **Note**
+>
+> 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/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md).
+
+Once you understand how to enable a connector, you can apply that knowledge to any other connector.
+
+## Enable the exporting engine
+
+Use `edit-config` from your [Netdata config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory) to edit `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](/docs/netdata-agent/start-stop-restart.md) to initiate exporting to your OpenTSDB database. The Netdata Agent continuously exports metrics collected from the moment it starts. You can expect to see data appear in your OpenTSDB database within seconds of restarting the Agent.
+
+Any further configuration is optional, based on your needs and the configuration of your OpenTSDB database. See the [OpenTSDB connector doc](/src/exporting/opentsdb/README.md) and [exporting engine reference](/src/exporting/README.md#configuration) for details.