Add frontmatter to exporting connectors (#9052)
Joel Hans committed
May 15, 2020 at 08:38 UTC
415c83a6bcd49c90b4ae6cd85aa30a6637ce3824
5 files changed
+22
-10
exporting/README.md
+2
-3
@@ -1,8 +1,7 @@
1
<!--
2
----
3
-title: "Exporting metrics to external databases (experimental)"
2
+title: "Export metrics to external databases (experimental)"
3
+description: "With the exporting engine, you can archive your Netdata metrics to multiple external databases for long-term storage or further analysis."
4
custom_edit_url: https://github.com/netdata/netdata/edit/master/exporting/README.md
5
----
5
-->
6
7
# Exporting metrics to external databases (experimental)
exporting/aws_kinesis/README.md
+2
-2
@@ -1,8 +1,8 @@
1
<!--
2
----
2
title: "Export metrics to AWS Kinesis Data Streams"
3
+description: "Archive your Agent's metrics to AWS Kinesis Data Streams for long-term storage, further analysis, or correlation with data from other sources."
4
custom_edit_url: https://github.com/netdata/netdata/edit/master/exporting/aws_kinesis/README.md
5
----
5
+sidebar_label: AWS Kinesis Data Streams
6
-->
7
8
# Export metrics to AWS Kinesis Data Streams
exporting/mongodb/README.md
+8
-1
@@ -1,4 +1,11 @@
1
-# MongoDB exporting connector
1
+<!--
2
+title: "Export metrics to MongoDB"
3
+description: "Archive your Agent's metrics to a MongoDB database for long-term storage, further analysis, or correlation with data from other sources."
4
+custom_edit_url: https://github.com/netdata/netdata/edit/master/exporting/mongodb/README.md
5
+sidebar_label: MongoDB
6
+-->
7
+
8
+# Export metrics to MongoDB
9
10
You can use the MongoDB connector and the experimental [exporting engine](../README.md) to archive your agent's metrics
11
to a MongoDB database for long-term storage, further analysis, or correlation with data from other sources.
exporting/prometheus/remote_write/README.md
+7
@@ -1,3 +1,10 @@
1
+<!--
2
+title: "Export metrics to Prometheus remote write providers"
3
+description: "Send Netdata metrics to your choice of more than 20 external storage providers for long-term archiving and further analysis."
4
+custom_edit_url: https://github.com/netdata/netdata/edit/master/exporting/prometheus/remote_write/README.md
5
+sidebar_label: Prometheus remote write
6
+-->
7
+
8
# Prometheus remote write exporting connector
9
10
The Prometheus remote write exporting connector uses the exporting engine to send Netdata metrics to your choice of more
exporting/pubsub/README.md
+3
-4
@@ -1,8 +1,8 @@
1
<!--
2
----
2
title: "Export metrics to Google Cloud Pub/Sub Service"
3
+description: "Export Netdata metrics to the Google Cloud Pub/Sub Service for long-term archiving or analytical processing."
4
custom_edit_url: https://github.com/netdata/netdata/edit/master/exporting/pubsub/README.md
5
----
5
+sidebar_label: Google Cloud Pub/Sub Service
6
-->
7
8
# Export metrics to Google Cloud Pub/Sub Service
@@ -30,8 +30,7 @@ and set the following options:
30
31
Set the `destination` option to a Pub/Sub service endpoint. `pubsub.googleapis.com` is the default one.
32
33
-Next, create the credentials JSON file by following Google Cloud's [authentication guide]
34
-(https://cloud.google.com/docs/authentication/getting-started#creating_a_service_account). The user running the Agent
33
+Next, create the credentials JSON file by following Google Cloud's [authentication guide](https://cloud.google.com/docs/authentication/getting-started#creating_a_service_account). The user running the Agent
34
(typically `netdata`) needs read access to `google_cloud_credentials.json`, which you can set with
35
`chmod 400 google_cloud_credentials.json; chown netdata google_cloud_credentials.json`. Set the `credentials file`
36
option to the full path of the file.