Search results for prometheus exporter

prometheus-rabbitmq-exporter-1.0.0-0.4.git40d9c32.lbn36.x86_64

Prometheus exporter for RabbitMQ metrics.

prometheus-redis-exporter-1.44.0-0.1.git9f7b036.lbn36.x86_64

Prometheus Exporter for Redis Metrics. Supports Redis 2.x, 3.x, 4.x, 5.x and 6.x

prometheus-squid-exporter-1.10.3-0.1.git7693646.lbn36.x86_64

Prometheus Exporter Squid

prometheus-statsd-exporter-0.26.0-1.lbn36.x86_64

statsd_exporter receives StatsD-style metrics and exports them as Prometheus metrics. Overview With StatsD 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. +----------+ +-------------------+ +--------------+ | StatsD |---(UDP/TCP repeater)--->| statsd_exporter |<---(scrape /metrics)---| Prometheus | +----------+ +-------------------+ +--------------+ Without StatsD Since the StatsD exporter uses the same line protocol as StatsD itself, you can also configure your applications to send StatsD metrics directly to the exporter. In that case, you don't need to run a StatsD server anymore. We recommend this only as an intermediate solution and recommend switching to native Prometheus instrumentation in the long term. Tagging Extensions The exporter supports Librato, InfluxDB, and DogStatsD-style tags, which will be converted into Prometheus labels. For Librato-style tags, they must be appended to the metric name with a delimiting #, as so: metric.name#tagName=val,tag2Name=val2:0|c See the statsd-librato-backend README for a more complete description. For InfluxDB-style tags, they must be appended to the metric name with a delimiting comma, as so: metric.name,tagName=val,tag2Name=val2:0|c See this InfluxDB blog post for a larger overview. For DogStatsD-style tags, they're appended as a |# delimited section at the end of the metric, as so: metric.name:0|c|#tagName=val,tag2Name=val2 See Tags in the DogStatsD documentation for the concept description and Datagram Format. If you encounter problems, note that this tagging style is incompatible with the original statsd implementation. Be aware: If you mix tag styles (e.g., Librato/InfluxDB with DogStatsD), the exporter will consider this an error and the sample will be discarded. Also, tags without values (#some_tag) are not supported and will be ignored.

prometheus-node-exporter-0.18.0-0.lbn25.x86_64

Prometheus exporter for machine metrics, written in Go with pluggable metric collectors. Collectors There is varying support for collectors on each operating system. The tables below list all existing collectors and the supported systems. Which collectors are used is controlled by the --collectors.enabled flag. Enabled by default Name Description OS conntrack Shows conntrack statistics (does nothing if no /proc/sys/net/netfilter/ present). Linux cpu Exposes CPU statistics FreeBSD diskstats Exposes disk I/O statistics from /proc/diskstats. Linux entropy Exposes available entropy. Linux filefd Exposes file descriptor statistics from /proc/sys/fs/file-nr. Linux filesystem Exposes filesystem statistics, such as disk space used. FreeBSD, Dragonfly, Linux, OpenBSD loadavg Exposes load average. Darwin, Dragonfly, FreeBSD, Linux, NetBSD, OpenBSD, Solaris mdadm Exposes statistics about devices in /proc/mdstat (does nothing if no /proc/mdstat present). Linux meminfo Exposes memory statistics. Dragonfly, FreeBSD, Linux netdev Exposes network interface statistics such as bytes transferred. Dragonfly, FreeBSD, Linux, OpenBSD netstat Exposes network statistics from /proc/net/netstat. This is the same information as netstat -s. Linux stat Exposes various statistics from /proc/stat. This includes CPU usage, boot time, forks and interrupts. Linux textfile Exposes statistics read from local disk. The --collector.textfile.directory flag must be set. any time Exposes the current system time. any vmstat Exposes statistics from /proc/vmstat. Linux Disabled by default Name Description OS bonding Exposes the number of configured and active slaves of Linux bonding interfaces. Linux devstat Exposes device statistics FreeBSD gmond Exposes statistics from Ganglia. any interrupts Exposes detailed interrupts statistics. Linux, OpenBSD ipvs Exposes IPVS status from /proc/net/ip_vs and stats from /proc/net/ip_vs_stats. Linux ksmd Exposes kernel and system statistics from /sys/kernel/mm/ksm. Linux logind Exposes session counts from logind. Linux megacli Exposes RAID statistics from MegaCLI. Linux meminfo_numa Exposes memory statistics from /proc/meminfo_numa. Linux ntp Exposes time drift from an NTP server. any runit Exposes service status from runit. any supervisord Exposes service status from supervisord. any systemd Exposes service and system status from systemd. Linux tcpstat Exposes TCP connection status information from /proc/net/tcp and /proc/net/tcp6. (Warning: the current version has potential performance issues in high load situations.) Linux Textfile Collector The textfile collector is similar to the Pushgateway, in that it allows exporting of statistics from batch jobs. It can also be used to export static metrics, such as what role a machine has. The Pushgateway should be used for service-level metrics. The textfile module is for metrics that are tied to a machine. To use it, set the --collector.textfile.directory flag on the Node exporter. The collector will parse all files in that directory matching the glob *.prom using the text format.

prometheus-node-exporter-0.18.0-0.lbn25.x86_64

Prometheus exporter for machine metrics, written in Go with pluggable metric collectors. Collectors There is varying support for collectors on each operating system. The tables below list all existing collectors and the supported systems. Which collectors are used is controlled by the --collectors.enabled flag. Enabled by default Name Description OS conntrack Shows conntrack statistics (does nothing if no /proc/sys/net/netfilter/ present). Linux cpu Exposes CPU statistics FreeBSD diskstats Exposes disk I/O statistics from /proc/diskstats. Linux entropy Exposes available entropy. Linux filefd Exposes file descriptor statistics from /proc/sys/fs/file-nr. Linux filesystem Exposes filesystem statistics, such as disk space used. FreeBSD, Dragonfly, Linux, OpenBSD loadavg Exposes load average. Darwin, Dragonfly, FreeBSD, Linux, NetBSD, OpenBSD, Solaris mdadm Exposes statistics about devices in /proc/mdstat (does nothing if no /proc/mdstat present). Linux meminfo Exposes memory statistics. Dragonfly, FreeBSD, Linux netdev Exposes network interface statistics such as bytes transferred. Dragonfly, FreeBSD, Linux, OpenBSD netstat Exposes network statistics from /proc/net/netstat. This is the same information as netstat -s. Linux stat Exposes various statistics from /proc/stat. This includes CPU usage, boot time, forks and interrupts. Linux textfile Exposes statistics read from local disk. The --collector.textfile.directory flag must be set. any time Exposes the current system time. any vmstat Exposes statistics from /proc/vmstat. Linux Disabled by default Name Description OS bonding Exposes the number of configured and active slaves of Linux bonding interfaces. Linux devstat Exposes device statistics FreeBSD gmond Exposes statistics from Ganglia. any interrupts Exposes detailed interrupts statistics. Linux, OpenBSD ipvs Exposes IPVS status from /proc/net/ip_vs and stats from /proc/net/ip_vs_stats. Linux ksmd Exposes kernel and system statistics from /sys/kernel/mm/ksm. Linux logind Exposes session counts from logind. Linux megacli Exposes RAID statistics from MegaCLI. Linux meminfo_numa Exposes memory statistics from /proc/meminfo_numa. Linux ntp Exposes time drift from an NTP server. any runit Exposes service status from runit. any supervisord Exposes service status from supervisord. any systemd Exposes service and system status from systemd. Linux tcpstat Exposes TCP connection status information from /proc/net/tcp and /proc/net/tcp6. (Warning: the current version has potential performance issues in high load situations.) Linux Textfile Collector The textfile collector is similar to the Pushgateway, in that it allows exporting of statistics from batch jobs. It can also be used to export static metrics, such as what role a machine has. The Pushgateway should be used for service-level metrics. The textfile module is for metrics that are tied to a machine. To use it, set the --collector.textfile.directory flag on the Node exporter. The collector will parse all files in that directory matching the glob *.prom using the text format.

python3-opentelemetry-exporter-prometheus-1.12.0rc1-1.lbn36.noarch

This library allows to export metrics data to Prometheus. Installation pip install opentelemetry-exporter-prometheus References OpenTelemetry Prometheus Exporter Prometheus OpenTelemetry Project

python3-prometheus-flask-exporter-0.20.3-1.lbn36.noarch

This library provides HTTP request metrics to export into Prometheus. It can also track method invocations using convenient functions. The following metrics are exported by default (unless the export_defaults is set to False). * flask_http_request_duration_seconds (Histogram) Labels: method, path and status. Flask HTTP request duration in seconds for all Flask requests. * flask_http_request_total (Counter) Labels: method and status. Total number of HTTP requests for all Flask requests. * flask_http_request_exceptions_total (Counter) Labels: method and status. Total number of uncaught exceptions when serving Flask requests. * flask_exporter_info (Gauge) Information about the Prometheus Flask exporter itself (e.g. version).

prometheus-pushgateway-0.3.0-1.gitc3b9ef4.lbn19.x86_64

The Prometheus Pushgateway exists to allow ephemeral and batch jobs to expose their metrics to Prometheus. Since these kinds of jobs may not exist long enough to be scraped, they can instead push their metrics to a Pushgateway. The Pushgateway then exposes these metrics to Prometheus. The Pushgateway is explicitly not an aggregator, but rather a metrics cache. It does not have a statsd-like semantics. The metrics pushed are exactly the same as you would present for scraping in a permanently running program. For machine-level metrics, the textfile collector of the Node exporter is usually more appropriate. The Pushgateway is best used for service-level metrics.

prometheus-snmp-exporter-0.0.5-1.lbn19.noarch

See https://github.com/prometheus/snmp_exporter/blob/master/README.md for documentation.