Prometheus Exporter Quickstarts on Grafana Labs

Elasticsearch Exporter

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

The following quickstart provides setup instructions and preconfigured dashboards, alerting rules, and recording rules for Elasticsearch Exporter. After running through the steps in this quickstart, you will have:

Set up and configured Elasticsearch Exporter to collect Elasticsearch metrics like cluster status, active shards, JVM metrics, Elasticsearch load. Elasticsearch Exporter will expose these as Prometheus-style metrics.
Configured Prometheus to scrape Elasticsearch Exporter metrics and optionally ship them to Grafana Cloud.
Set up a preconfigured and curated set of recording rules to cache frequent Prometheus queries.
Imported Grafana dashboards to visualize your metrics data.
Set up Prometheus alerting rules to alert on your metrics data.

Metrics usage

This exporter publishes roughly 392 Prometheus time series by default. To see a list of metrics shipped by default with this exporter, please download a sample metrics scrape here.

Note that depending on its configuration, Elasticsearch Exporter may collect and publish far more metrics than this default set. To learn more about configuring Elasticsearch Exporter and toggling its collectors, please see the Elasticsearch Exporter GitHub repository.

Beyond toggling Elasticsearch Exporter’s settings, you can reduce metrics usage by dropping time series you don’t need to store in Prometheus or Grafana Cloud. To learn how to do this, please see Reducing Prometheus metrics usage with relabeling from the Grafana Cloud docs.

Grafana Cloud’s Elasticsearch Integration

If you’re using Grafana Cloud, you can skip all of the steps in this guide by installing the Elasticsearch Exporter Integration, which is designed to help you get up and running in a few commands and clicks. Sign up for free.

To learn how to set up Elasticsearch Exporter using the Elasticsearch Exporter Integration, please see Elasticsearch Exporter Integration from the Grafana Cloud docs.

MySQL Server Exporter

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

The following quickstart provides setup instructions and preconfigured dashboards, alerting rules, and recording rules for the MySQL Exporter. After running through the steps in this quickstart, you will have:

Set up and configured MySQL Exporter to collect MySQL metrics like queries per second (QPS) and InnoDB buffer pool size. MySQL Exporter will expose these as Prometheus-style metrics.
Configured Prometheus to scrape MySQL Exporter metrics and optionally ship them to Grafana Cloud.
Set up a preconfigured and curated set of recording rules to cache frequent queries.
Imported Grafana dashboards to visualize your metrics data.
Set up Prometheus alerting rules to alert on your metrics data.

Metrics usage

This exporter publishes roughly 1000 Prometheus time series by default. To see a list of metrics shipped by default with this exporter, please download a sample metrics scrape here.

Note that depending on its configuration, MySQL Exporter may collect and publish far more metrics than this default set. To learn more about configuring MySQL Exporter and toggling its collectors, please see the MySQL Exporter GitHub repository.

Beyond toggling MySQL Exporter’s settings, you can reduce metrics usage by dropping time series you don’t need to store in Prometheus or Grafana Cloud. To learn how to do this, please see Reducing Prometheus metrics usage with relabeling from the Grafana Cloud docs.

Grafana Cloud’s Linux Node Integration

If you’re using Grafana Cloud, you can skip all of the steps in this guide by installing the MySQL Integration, which is designed to help you get up and running in a few commands and clicks. Sign up for free.

To learn how to get MySQL metrics using the MySQL Integration, please see MySQL Integration from the Grafana Cloud docs.

Node exporter

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

The following quickstart provides setup instructions and preconfigured dashboards, alerting rules, and recording rules for Node Exporter. After running through the steps in this quickstart, you will have:

Set up and configured Node Exporter to collect Linux system metrics like CPU load and disk I/O. Node Exporter will expose these as Prometheus-style metrics.
Configured Prometheus to scrape Node Exporter metrics and optionally ship them to Grafana Cloud.
Set up a preconfigured and curated set of recording rules to cache frequent queries.
Imported Grafana dashboards to visualize your metrics data.
Set up Prometheus alerting rules to alert on your metrics data.

Metrics usage

This exporter publishes roughly 500 Prometheus time series by default. To see a list of metrics shipped by default with this exporter, please download a sample metrics scrape here.

Note that depending on its configuration, Node Exporter may collect and publish far more metrics than this default set. To learn more about configuring Node Exporter and toggling its collectors, please see the Node Exporter GitHub repository.

Beyond toggling Node Exporter’s settings, you can reduce metrics usage by dropping time series you don’t need to store in Prometheus or Grafana Cloud. To learn how to do this, please see Reducing Prometheus metrics usage with relabeling from the Grafana Cloud docs.

Grafana Cloud’s Linux Node Integration

If you’re using Grafana Cloud, you can skip all of the steps in this guide by installing the Linux Server Integration, which is designed to help you get up and running in a few commands and clicks. Sign up for free.

To learn how to set up Node Exporter using the Linux Server Integration, please see Monitoring a Linux host using the Linux host integration from the Grafana Cloud docs.

Node.js Exporter

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

The following quickstart provides setup instructions and preconfigured dashboards, alerting rules, and recording rules for the prom-client for Node.js Prometheus metrics exporter. After running through the steps in this quickstart, you will have:

Set up and configured prom-client for Node.js to collect Node.js app metrics like event loop lag, active handles, and GC metrics. prom-client for Node.js will expose these as Prometheus-style metrics.
Configured Prometheus to scrape prom-client for Node.js metrics and optionally ship them to Grafana Cloud.
Set up a preconfigured and curated set of recording rules to cache frequent Prometheus queries.
Imported Grafana dashboards to visualize your metrics data.
Set up Prometheus alerting rules to alert on your metrics data.

Metrics usage

This exporter publishes roughly 78 Prometheus time series by default. To see a list of metrics shipped by default with this exporter, please download a sample metrics scrape here.

Note that depending on its configuration, prom-client for Node.js may collect and publish far more metrics than this default set. To learn more about configuring prom-client for Node.js and toggling its collectors, please see the prom-client for Node.js GitHub repository.

Beyond toggling prom-client for Node.js’s settings, you can reduce metrics usage by dropping time series you don’t need to store in Prometheus or Grafana Cloud. To learn how to do this, please see Reducing Prometheus metrics usage with relabeling from the Grafana Cloud docs.

Grafana Cloud’s Node.js Integration

If you’re using Grafana Cloud, you can skip all of the steps in this guide by installing the Node.js Integration, which is designed to help you get up and running in a few commands and clicks. Sign up for free.

To learn how to collect Node.js metrics using the Node.js Integration, please see Node.js Integration from the Grafana Cloud docs.

Postgres Exporter

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

The following quickstart provides setup instructions and preconfigured dashboards and alerting rules for the Postgres Exporter. After running through the steps in this quickstart, you will have:

Set up and configured Postgres Exporter to collect Postgres metrics like queries per second (QPS) and rows fetched/returned/inserted/updated/deleted per second. Postgres Exporter will expose these as Prometheus-style metrics.
Configured Prometheus to scrape Postgres Exporter metrics and optionally ship them to Grafana Cloud.
Imported Grafana dashboards to visualize your metrics data.
Set up Prometheus alerting rules to alert on your metrics data.

Metrics usage

This exporter publishes roughly 450 Prometheus time series by default. To see a list of metrics shipped by default with this exporter, please download a sample metrics scrape here.

Note that depending on its configuration, Postgres Exporter may collect and publish far more metrics than this default set. To learn more about configuring Postgres Exporter and toggling its collectors, please see the Postgres Exporter GitHub repository.

Beyond toggling Postgres Exporter’s settings, you can reduce metrics usage by dropping time series you don’t need to store in Prometheus or Grafana Cloud. To learn how to do this, please see Reducing Prometheus metrics usage with relabeling from the Grafana Cloud docs.

Grafana Cloud’s Postgres Exporter Integration

If you’re using Grafana Cloud, you can skip all of the steps in this guide by installing the Postgres Exporter Integration, which is designed to help you get up and running in a few commands and clicks. Sign up for free.

To learn how to set up Postgres Exporter using the Postgres Exporter Integration, please see Postgres Exporter Integration from the Grafana Cloud docs.

Prometheus Go Client Library

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

The following quickstart provides setup instructions and a preconfigured dashboard for the Prometheus Go client library. After running through the steps in this quickstart, you will have:

Set up and configured the Go client library to collect Go Prometheus metrics like total reserved memory, stack memory use, and heap memory. The Go client library will expose these as Prometheus-style metrics.
Configured Prometheus to scrape Go client library metrics and optionally ship them to Grafana Cloud.
Imported Grafana dashboards to visualize your metrics data.

Metrics usage

This exporter publishes roughly 45 Prometheus time series by default. To see a list of metrics shipped by default with this exporter, please download a sample metrics scrape here.

Note that depending on its configuration, Prometheus Go client library may collect and publish far more metrics than this default set. To learn more about configuring Prometheus Go client library and toggling its collectors, please see the Prometheus Go client library GitHub repository.

Beyond toggling Prometheus Go client library’s settings, you can reduce metrics usage by dropping time series you don’t need to store in Prometheus or Grafana Cloud. To learn how to do this, please see Reducing Prometheus metrics usage with relabeling from the Grafana Cloud docs.

Grafana Cloud’s Golang Integration

If you’re using Grafana Cloud, you can skip all of the steps in this guide by installing the Prometheus Go Integration, which is designed to help you get up and running in a few commands and clicks. Sign up for free.

To learn how to set up Prometheus Go client library with the Prometheus Go Integration, please see Go Integration from the Grafana Cloud docs.

Redis Exporter

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

The following quickstart provides setup instructions and preconfigured dashboards, alerting rules, and recording rules for Redis Exporter. After running through the steps in this quickstart, you will have:

Set up and configured Redis Exporter to collect Redis metrics like Redis uptime, commands executed per second, memory utilization, and more. Most items from the redis info command are exported. Redis Exporter will expose these as Prometheus-style metrics.
Configured Prometheus to scrape Redis Exporter metrics and optionally ship them to Grafana Cloud.
Set up a preconfigured and curated set of recording rules to cache frequent Prometheus queries.
Imported Grafana dashboards to visualize your metrics data.
Set up Prometheus alerting rules to alert on your metrics data.

Metrics usage

This exporter publishes roughly 190 Prometheus time series by default. To see a list of metrics shipped by default with this exporter, please download a sample metrics scrape here.

Note that depending on its configuration, Redis Exporter may collect and publish far more metrics than this default set. To learn more about configuring Redis Exporter and toggling its collectors, please see the Redis Exporter GitHub repository.

Beyond toggling Redis Exporter’s settings, you can reduce metrics usage by dropping time series you don’t need to store in Prometheus or Grafana Cloud. To learn how to do this, please see Reducing Prometheus metrics usage with relabeling from the Grafana Cloud docs.

Grafana Cloud’s Redis Exporter Integration

If you’re using Grafana Cloud, you can skip all of the steps in this guide by installing the Redis Exporter Integration, which is designed to help you get up and running in a few commands and clicks. Sign up for free.

To learn how to set up Redis Exporter using the Redis Exporter Integration, please see Redis Exporter Integration from the Grafana Cloud docs.