Displaying 1 to 20 from 103 results

node_exporter - Exporter for machine metrics

  •    Go

Prometheus exporter for hardware and OS metrics exposed by *NIX kernels, written in Go with pluggable metric collectors.The WMI exporter is recommended for Windows users.

redis_exporter - Prometheus Exporter for Redis Metrics. Supports Redis 2.x, 3.x and 4.x

  •    Go

and adjust the host name accordingly. Here is an example Kubernetes deployment configuration for how to deploy the redis_exporter as a sidecar with a Redis instance.

wmi_exporter - Prometheus exporter for Windows machines using WMI

  •    Go

Prometheus exporter for Windows machines, using the WMI (Windows Management Instrumentation). See the linked documentation on each collector for more information on reported metrics, configuration settings and usage examples.

blackbox_exporter - Blackbox prober exporter

  •    Go

The blackbox exporter allows blackbox probing of endpoints over HTTP, HTTPS, DNS, TCP and ICMP.Visiting http://localhost:9115/probe?target=google.com&module=http_2xx will return metrics for a HTTP probe against google.com. The probe_success metric indicates if the probe succeeded. Adding a debug=true parameter will return debug information for that probe.




kafka_exporter - Kafka exporter for Prometheus

  •    Go

Kafka exporter for Prometheus. For other metrics from Kafka, have a look at the JMX exporter. Support Apache Kafka version 0.10.1.0 (and later).

consul_exporter - Exporter for Consul metrics

  •    Go

Export Consul service health to Prometheus.This exporter supports grabbing key/value pairs from Consul's KV store and exposing them to Prometheus. This can be useful, for instance, if you use Consul KV to store your intended cluster size, and want to graph that value against the actual value found via monitoring.

haproxy_exporter - Simple server that scrapes HAProxy stats and exports them via HTTP for Prometheus consumption

  •    Go

This is a simple server that scrapes HAProxy stats and exports them via HTTP for Prometheus consumption.For more information check the source code documentation. All of the core developers are accessible via the Prometheus Developers mailinglist.


memcached_exporter - Exports metrics from memcached servers for consumption by Prometheus.

  •    Go

A memcached exporter for prometheus.The memcached exporter exports metrics from a memcached server for consumption by prometheus. The server is specified as --memcached.address flag to the program (default is localhost:11211).

snmp_exporter - SNMP Exporter for Prometheus

  •    Go

This is an exporter that exposes information gathered from SNMP for use by the Prometheus monitoring system.There are two components. An exporter that does the actual scraping, and a generator (which depends on NetSNMP) that creates the configuration for use by the exporter.

statsd_exporter - StatsD to Prometheus metrics exporter

  •    Go

statsd_exporter receives StatsD-style metrics and exports them as Prometheus metrics.To pipe metrics from an existing StatsD environment into Prometheus, configure StatsD's repeater backend to repeat all received metrics to a statsd_exporter process. This exporter translates StatsD metrics to Prometheus metrics via configured mapping rules.

prometheus_async - Async helpers for prometheus_client.

  •    Python

prometheus_async adds support for asynchronous frameworks to the official Python client for the Prometheus metrics and monitoring system. Currently asyncio (Python 3.4, 3.5, 3.6) and Twisted (Python 2.7, 3.4, 3.5, 3.6, PyPy) are supported.

kafka_zookeeper_exporter - Prometheus exporter for Kafka cluster state stored in ZooKeeper

  •    Go

A daemon that exposes Kafka cluster state stored in ZooKeeper. Metrics exported by kafka_zookeeper_exporter provide cluster level overview of the entire cluster and can be used along jmx_exporter which provides broker level data. jmx_exporter exports what each brokers believes to be true, but this information can be incorrect in case of a network partition or other split brain issues. ZooKeeper on the other hand is the source of truth for the entire cluster configuration and runtime status, so the metrics exported from it are the best representation of the entire cluster status.

sidekiq-prometheus-exporter - All the basic metrics of Sidekiq prepared for Prometheus

  •    Ruby

Open dashboard example file, then open https://<your grafana-url>/dashboard/import and paste the content of the file.

prometheus-pve-exporter - Exposes information gathered from Proxmox VE cluster for use by the Prometheus monitoring system

  •    Python

This is an exporter that exposes information gathered from Proxmox VE node for use by the Prometheus monitoring system. Use :: for the address argument in order to bind to both IPv6 and IPv4 sockets on dual stacked machines.

digitalocean_exporter - Prometheus exporter for DigitalOcean metrics, written in Go.

  •    Go

Prometheus exporter for various metrics about your DigitalOcean droplets, volumes, snapshots & networks and much more, written in Go. Example docker-compose.yml with Transmission also running in docker.

ebpf_exporter - Prometheus exporter for custom eBPF metrics

  •    Go

Prometheus exporter for custom eBPF metrics. Motivation of this exporter is to allow you to write eBPF code and export metrics that are not otherwise accessible from the Linux kernel.