diff options
Diffstat (limited to 'exporting/WALKTHROUGH.md')
| -rw-r--r-- | exporting/WALKTHROUGH.md | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/exporting/WALKTHROUGH.md b/exporting/WALKTHROUGH.md index 0612b298a..5afd26045 100644 --- a/exporting/WALKTHROUGH.md +++ b/exporting/WALKTHROUGH.md @@ -1,8 +1,11 @@ <!-- title: "Exporting to Netdata, Prometheus, Grafana stack" description: "Using Netdata in conjunction with Prometheus and Grafana." -custom_edit_url: https://github.com/netdata/netdata/edit/master/exporting/WALKTHROUGH.md -sidebar_label: Netdata, Prometheus, Grafana stack +custom_edit_url: "https://github.com/netdata/netdata/edit/master/exporting/WALKTHROUGH.md" +sidebar_label: "Netdata, Prometheus, Grafana stack" +learn_status: "Published" +learn_topic_type: "Tasks" +learn_rel_path: "Setup/Exporting connectors" --> # Netdata, Prometheus, Grafana stack @@ -64,7 +67,7 @@ command to run (`/bin/bash`) and then chooses the base container images (`centos be sitting inside the shell of the container. After we have entered the shell we can install Netdata. This process could not be easier. If you take a look at [this -link](/packaging/installer/README.md), the Netdata devs give us several one-liners to install Netdata. I have not had +link](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md), the Netdata devs give us several one-liners to install Netdata. I have not had any issues with these one liners and their bootstrapping scripts so far (If you guys run into anything do share). Run the following command in your container. @@ -223,7 +226,7 @@ the `chart` dimension. If you'd like you can combine the `chart` and `instance` Let's give this a try: `netdata_system_cpu_percentage_average{chart="system.cpu", instance="netdata:19999"}` This is the basics of using Prometheus to query Netdata. I'd advise everyone at this point to read [this -page](/exporting/prometheus/README.md#using-netdata-with-prometheus). The key point here is that Netdata can export metrics from +page](https://github.com/netdata/netdata/blob/master/exporting/prometheus/README.md#using-netdata-with-prometheus). The key point here is that Netdata can export metrics from its internal DB or can send metrics _as-collected_ by specifying the `source=as-collected` URL parameter like so. <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes&types=yes&source=as-collected> If you choose to use this method you will need to use Prometheus's set of functions here: <https://prometheus.io/docs/querying/functions/> to |