Commonly used Prometheus exporters and their recommended ports: Difference between revisions

From Jwiki
← Older editNewer edit →
No edit summary
No edit summary
Line 1: Line 1:
[[Category:Prometheus]]
= Commonly used Prometheus exporters and their recommended ports =
[[Category:Snippets & Notes]]
 
This page serves as a centralized reference for the default and recommended TCP ports used by various Prometheus exporters. The goal is to maintain consistency and avoid port conflicts across our monitoring infrastructure.
 
== Guiding Principles ==
* '''IANA Unofficial Ports''': The port range `9100-9999` is the community-accepted range for monitoring exporters. We will adhere to this where possible [36].
* '''Consistency is Key''': When a de facto standard port exists (e.g., `9100` for `node_exporter`), we will use it [39].
* '''Clarity Over Brevity''': For complex tools, a brief explanation is better than a single, potentially misleading port number.
 
----
 
== Core Infrastructure & Virtualization ==
These exporters monitor the fundamental layers of our stack, from physical hosts and hypervisors to container orchestration.
 
{| class="wikitable"
{| class="wikitable"
|+ Core Infrastructure
|-
! Exporter
! Exporter
! Recommended Port
! Recommended Port
! Notes
! Notes
|-
|-
| Node Exporter
| '''Node Exporter'''
| 9100
| 9100
| Linux/Unix host metrics (universal)
| For Linux/Unix host metrics (CPU, RAM, disk, network). Universal and essential.
|-
|-
| Grafana Alloy
| '''Windows Exporter'''
| 9101
| 9109
| Vendor-neutral OpenTelemetry agent for metrics, logs, & traces; can replace multiple exporters. (Default agent UI/API port: 12345)
| The equivalent of the Node Exporter for Windows hosts.
|-
|-
| Blackbox Exporter
| '''Proxmox Exporter'''
| 9102
| 9105
| Probing endpoints (ICMP/HTTP/TCP/SSL)
| For Proxmox VE metrics (hypervisor, VM/container status, storage).
|-
|-
| cAdvisor
| '''cAdvisor'''
| 9103
| 9103
| Container metrics (K8s, Docker hosts)
| Provides container metrics. Essential on Kubernetes nodes and Docker hosts.
|-
|-
| kube-state-metrics
| '''kube-state-metrics'''
| 9104
| 9104
| Kubernetes resource/object metrics
| Exposes metrics about Kubernetes API objects (deployments, pods, services).
|-
|-
| Proxmox Exporter
| '''SNMP Exporter'''
| 9105
| 9120
| Proxmox VE (hypervisor, VM/container/storage metrics)
| For network and legacy equipment that exposes data via SNMP (switches, routers, printers).
|}
 
----
 
== Observability Agent: Grafana Alloy ==
Grafana Alloy is not a simple exporter but a powerful, vendor-neutral telemetry collector. It is designed to replace the need for multiple agents by handling metrics, logs, and traces in a single, configurable application.
 
* '''Role''': Alloy acts as a central pipeline. You configure it to scrape other exporters (like `node_exporter`), receive OpenTelemetry data, and tail log files. It can then process and forward this data to Prometheus, Loki, Tempo, or any OTLP-compatible backend.
* '''No Single "Exporter" Port''': Because Alloy connects to other targets, it doesn't have one single port it "serves" metrics on.
* '''Management UI''': Alloy runs a web interface for debugging and inspecting its components on port '''`12345`''' by default.
* '''Internal Metrics''': You can configure Alloy to expose its own internal performance metrics on a Prometheus endpoint. If you do this, assigning it a dedicated port like '''`9101`''' from your list is a good practice.
 
; When to use Alloy
: Consider using Alloy when you need to collect multiple types of telemetry (metrics, logs, traces), perform advanced filtering or relabeling, or standardize your data collection across different teams and environments. It simplifies your deployment by reducing the number of running agents.
 
----
 
== Databases & Caching ==
Exporters for common databases, caches, and data stores.
 
{| class="wikitable"
|+ Databases & Caching
|-
|-
| MySQL Exporter
! Exporter
| 9106
! Recommended Port
| MySQL/MariaDB databases
! Notes
|-
|-
| PostgreSQL Exporter
| '''PostgreSQL Exporter'''
| 9107
| 9107
| PostgreSQL databases
| For PostgreSQL databases.
|-
| '''MySQL Exporter'''
| 9106
| For MySQL and MariaDB databases.
|-
|-
| Redis Exporter
| '''Redis Exporter'''
| 9108
| 9108
| Redis in-memory database
| For Redis in-memory databases.
|-
| Windows Exporter
| 9109
| Windows hosts
|-
|-
| MongoDB Exporter
| '''MongoDB Exporter'''
| 9110
| 9110
| MongoDB databases
| For MongoDB databases.
|-
|-
| JMX Exporter
| '''Elasticsearch Exporter'''
| 9111
| 9118
| JVM metrics (Kafka, Cassandra, etc.)
| For Elasticsearch and OpenSearch clusters.
|}
 
----
 
== Applications & Services ==
Exporters for common applications, web servers, and other services.
 
{| class="wikitable"
|+ Applications & Services
|-
|-
| Apache Exporter
! Exporter
| 9112
! Recommended Port
| Apache HTTPD servers
! Notes
|-
|-
| NGINX Exporter
| '''Blackbox Exporter'''
| 9113
| 9102
| NGINX web/app servers
| For probing endpoints over HTTP, HTTPS, DNS, TCP, and ICMP to measure uptime.
|-
|-
| GitLab Exporter
| '''JMX Exporter'''
| 9114
| 9111
| GitLab application
| For any Java application using JMX (e.g., Kafka, Cassandra, ActiveMQ).
|-
|-
| GitLab Runner Exporter
| '''NGINX Exporter'''
| 9115
| 9113
| GitLab Runner agents
| For NGINX web and reverse proxy servers.
|-
|-
| RabbitMQ Exporter
| '''RabbitMQ Exporter'''
| 9116
| 9116
| RabbitMQ messaging
| For RabbitMQ messaging systems.
|}
 
<!--
== CI/CD & Development ==
Exporters for development tools and continuous integration pipelines.
 
{| class="wikitable"
|+ CI/CD
|-
|-
| Kafka Exporter
! Exporter
| 9117
! Recommended Port
| Apache Kafka
! Notes
|-
|-
| Elasticsearch Exporter
| '''GitLab Exporter'''
| 9118
| 9114
| Elasticsearch / OpenSearch
| For GitLab application metrics.
|-
|-
| HAProxy Exporter
| '''GitLab Runner Exporter'''
| 9119
| 9115
| HAProxy load balancer
| For GitLab Runner agents.
|-
| SNMP Exporter
| 9120
| Network/legacy equipment (switches/routers)
|-
| Script Exporter
| 9121
| Arbitrary shell scripts
|-
| Graphite Exporter
| 9122
| Importing old Graphite metrics
|-
| CloudWatch Exporter
| 9123
| AWS metrics
|-
| Azure Exporter
| 9124
| Azure cloud metrics
|-
| Stackdriver Exporter
| 9125
| Google Cloud Platform
|-
| PHP-FPM Exporter
| 9126
| PHP FastCGI server (WordPress, Magento, etc.)
|-
| rtrtr Exporter
| 9127
| (Rare) RPKI/routing
|-
| Memcached Exporter (official)
| 9128
| Memcached cache
|-
| Consul Exporter (official)
| 9129
| HashiCorp Consul service mesh
|-
| Oracle DB Exporter
| 9130
| Oracle Database
|-
| PgBouncer Exporter
| 9131
| PgBouncer connection pooler
|-
| ProxySQL Exporter
| 9132
| ProxySQL SQL proxy
|-
| SQL Exporter
| 9133
| Generic SQL queries
|-
| Aerospike Exporter
| 9134
| Aerospike NoSQL database
|-
| ClickHouse Exporter
| 9135
| ClickHouse columnar DB
|-
| AWS RDS Exporter
| 9136
| AWS RDS database service
|-
| Druid Exporter
| 9137
| Apache Druid analytics DB
|-
| RethinkDB Exporter
| 9138
| RethinkDB NoSQL DB
|-
| RavenDB Exporter
| 9139
| RavenDB NoSQL document DB
|-
| Tarantool Metric Library
| 9140
| Tarantool NoSQL
|-
| Twemproxy Exporter
| 9141
| Twitter’s Redis/Memcached proxy
|-
| BIND/BIND Query Exporter
| 9142
| BIND DNS server
|-
| Bitcoind Exporter
| 9143
| Bitcoin nodes
|-
| c-lightning Exporter
| 9144
| Lightning network (Bitcoin)
|-
| DHCPD Leases Exporter
| 9145
| DHCP server
|-
| Dovecot Exporter
| 9146
| Dovecot mail server
|-
| Dnsmasq Exporter
| 9147
| Dnsmasq DNS/DHCP server
|-
| eBPF Exporters
| 9148
| Linux kernel telemetry
|-
| Ethereum Client Exporter
| 9149
| Ethereum, Geth/Parity node metrics
|-
| JFrog Artifactory Exporter
| 9150
| JFrog Artifactory artifact server
|-
| Hostapd Exporter
| 9151
| Hostapd WiFi AP daemon
|-
| IPsec/IPset Exporter
| 9152
| Linux firewall and VPN
|-
| Linux HA (Pacemaker) Exporter
| 9153
| Pacemaker clusters
|-
| JMeter Plugin Exporter
| 9154
| JMeter performance tests
|-
| Kannel Exporter
| 9155
| Kannel SMS gateway
|-
| Kemp LoadBalancer Exporter
| 9156
| Kemp hardware load balancers
|-
| Kibana Exporter
| 9157
| Kibana dashboards
|-
| Locust Exporter
| 9158
| Locust load testing
|-
| Minecraft Exporter
| 9159
| Minecraft server mod
|-
| NetBird Exporter
| 9160
| NetBird VPN overlay
|-
| Nomad Exporter
| 9161
| HashiCorp Nomad
|-
| nftables Exporter
| 9162
| Linux firewall (nftables)
|-
| OpenStack/OVirt Exporters
| 9163
| Private cloud virtualization
|-
| OpenVPN Exporter
| 9164
| OpenVPN server
|-
| Podman Exporter
| 9165
| Podman container runtime
|-
| Prefect2 Exporter
| 9166
| Prefect 2 workflow engine
|-
| Process Exporter
| 9167
| Linux process details
|-
| rTorrent Exporter
| 9168
| rTorrent BitTorrent client
|-
| Rundeck Exporter
| 9169
| Rundeck Ops automation
|-
| SABnzbd Exporter
| 9170
| SABnzbd Usenet downloader
|-
| SAML Exporter
| 9171
| SAML SSO authentication
|-
| Shield Exporter
| 9172
| SHIELD backup software
|-
| Smokeping Prober
| 9173
| Latency and reachability
|-
| SMTP/Maildir MDA Exporters
| 9174
| Mail delivery daemons
|-
| SoftEther Exporter
| 9175
| SoftEther VPN
|-
| SSH Exporter
| 9176
| SSH server/client
|-
| Teamspeak3 Exporter
| 9177
| Teamspeak VoIP server
|-
| Transmission Exporter
| 9178
| Transmission BitTorrent client
|-
| Unbound Exporter
| 9179
| Unbound DNS resolver
|-
| WireGuard Exporter
| 9180
| WireGuard VPN
|-
| Xen Exporter
| 9181
| Xen virtualization
|-
| Manticore Search Exporter
| 9182
| Manticore Search (open source search engine)
|-
| Beanstalkd Exporter
| 9183
| Beanstalkd queue systems
|-
| EMQ Exporter
| 9184
| EMQX MQTT broker
|-
| Gearman Exporter
| 9185
| Gearman job server
|-
| IBM MQ Exporter
| 9186
| IBM MQ message queues
|-
| NATS Exporter
| 9187
| NATS messaging systems
|-
| NSQ Exporter
| 9188
| NSQ queue/messaging
|-
| Mirth Connect Exporter
| 9189
| Mirth Connect (healthcare integration)
|}
|}
-->
<!-- Add other categories as needed, such as "Cloud Services", "Networking", etc. -->
[[Category:Prometheus]]
[[Category:Snippets & Notes]]

Revision as of 16:11, 27 August 2025

Commonly used Prometheus exporters and their recommended ports

This page serves as a centralized reference for the default and recommended TCP ports used by various Prometheus exporters. The goal is to maintain consistency and avoid port conflicts across our monitoring infrastructure.

Guiding Principles

  • IANA Unofficial Ports: The port range `9100-9999` is the community-accepted range for monitoring exporters. We will adhere to this where possible [36].
  • Consistency is Key: When a de facto standard port exists (e.g., `9100` for `node_exporter`), we will use it [39].
  • Clarity Over Brevity: For complex tools, a brief explanation is better than a single, potentially misleading port number.

Core Infrastructure & Virtualization

These exporters monitor the fundamental layers of our stack, from physical hosts and hypervisors to container orchestration.

Core Infrastructure
Exporter Recommended Port Notes
Node Exporter 9100 For Linux/Unix host metrics (CPU, RAM, disk, network). Universal and essential.
Windows Exporter 9109 The equivalent of the Node Exporter for Windows hosts.
Proxmox Exporter 9105 For Proxmox VE metrics (hypervisor, VM/container status, storage).
cAdvisor 9103 Provides container metrics. Essential on Kubernetes nodes and Docker hosts.
kube-state-metrics 9104 Exposes metrics about Kubernetes API objects (deployments, pods, services).
SNMP Exporter 9120 For network and legacy equipment that exposes data via SNMP (switches, routers, printers).

Observability Agent: Grafana Alloy

Grafana Alloy is not a simple exporter but a powerful, vendor-neutral telemetry collector. It is designed to replace the need for multiple agents by handling metrics, logs, and traces in a single, configurable application.

  • Role: Alloy acts as a central pipeline. You configure it to scrape other exporters (like `node_exporter`), receive OpenTelemetry data, and tail log files. It can then process and forward this data to Prometheus, Loki, Tempo, or any OTLP-compatible backend.
  • No Single "Exporter" Port: Because Alloy connects to other targets, it doesn't have one single port it "serves" metrics on.
  • Management UI: Alloy runs a web interface for debugging and inspecting its components on port `12345` by default.
  • Internal Metrics: You can configure Alloy to expose its own internal performance metrics on a Prometheus endpoint. If you do this, assigning it a dedicated port like `9101` from your list is a good practice.
When to use Alloy
Consider using Alloy when you need to collect multiple types of telemetry (metrics, logs, traces), perform advanced filtering or relabeling, or standardize your data collection across different teams and environments. It simplifies your deployment by reducing the number of running agents.

Databases & Caching

Exporters for common databases, caches, and data stores.

Databases & Caching
Exporter Recommended Port Notes
PostgreSQL Exporter 9107 For PostgreSQL databases.
MySQL Exporter 9106 For MySQL and MariaDB databases.
Redis Exporter 9108 For Redis in-memory databases.
MongoDB Exporter 9110 For MongoDB databases.
Elasticsearch Exporter 9118 For Elasticsearch and OpenSearch clusters.

Applications & Services

Exporters for common applications, web servers, and other services.

Applications & Services
Exporter Recommended Port Notes
Blackbox Exporter 9102 For probing endpoints over HTTP, HTTPS, DNS, TCP, and ICMP to measure uptime.
JMX Exporter 9111 For any Java application using JMX (e.g., Kafka, Cassandra, ActiveMQ).
NGINX Exporter 9113 For NGINX web and reverse proxy servers.
RabbitMQ Exporter 9116 For RabbitMQ messaging systems.
Retrieved from "https://wiki.jandzsogyorgy.hu/index.php?title=Commonly_used_Prometheus_exporters_and_their_recommended_ports&oldid=284"