Commonly used Prometheus exporters and their recommended ports - Revision history

Gyurci08 at 16:22, 27 August 2025

2025-08-27T16:22:11Z

← Older revision		Revision as of 16:22, 27 August 2025
Line 1:		Line 1:
	= Prometheus Exporter Port Allocation Standard =		= Prometheus Exporter Port Allocation Standard =

	This document defines the '''official internal standard''' for Prometheus exporter port assignments within our infrastructure. The primary goal is to create a cohesive~~, consistent~~, and maintainable port scheme that prevents conflicts, is easy to understand, and ~~is simple to~~ extend.		This document defines the '''official internal standard''' for Prometheus exporter port assignments within our infrastructure. The primary goal is to create a single, cohesive, and maintainable port scheme that prevents conflicts and is easy to understand and extend.

	== Guiding Principles ==		== Guiding Principles ==
	* '''~~Internal Consistency is Priority~~''': This ~~list~~ is ~~our~~ single source of truth. ~~It overrides external community standards if they conflict~~ with ~~our internal scheme~~.		* '''One List, One Standard''': This page is the single source of truth. All services that expose a Prometheus metrics endpoint '''must''' be included in this list with a unique port.
	* '''~~Uniqueness~~ is ~~Mandatory~~''': ~~Every exporter in this~~ list ~~is assigned a unique port to prevent overlaps~~.		* '''Internal Consistency is Priority''': This list overrides external community standards or vendor defaults if they conflict with our internal, sequential scheme.
	* '''Logical Grouping''': Ports are allocated in logical, contiguous blocks, making the scheme predictable and easy to manage.		* '''Logical Grouping''': Ports are allocated in logical, contiguous blocks, making the scheme predictable and easy to manage.
	* '''Documentation First''': Before deploying a new exporter, it '''must''' be added to this list with an assigned port.		* '''Documentation First''': Before deploying a new exporter, it '''must''' be added to this list with an assigned port.
Line 11:		Line 11:
	----		----

	== ~~Special Case: Grafana Alloy ==~~		== Observability & Core Infrastructure (9100-9119) ==
	~~Grafana Alloy is our primary telemetry collector and is treated as a special case due to its unique role and well-known default port.~~		This block covers the foundational layer of our stack, from the observability agent itself to the hosts and orchestration platforms.

	* '''Role''': Alloy is configured to scrape other exporters on their assigned ports (defined below). It also receives OpenTelemetry data and tails log files.
	* '''Management UI Port''': The Alloy web UI for debugging and graph visualization will always run on its default port, '''`12345`''' [11].
	* '''Internal Metrics''': If Alloy is configured to expose its own internal metrics, it will be assigned a port from the standard block below, just like any other exporter.

	~~----~~

	== Core Infrastructure ~~& Orchestration~~ (9100-~~9109~~) ==
	This block covers the foundational layer of our stack, from the ~~hosts~~ to the orchestration platforms.

	{\| class="wikitable"		{\| class="wikitable"
Line 29:		Line 20:
	! Assigned Port		! Assigned Port
	! Notes		! Notes
			\|-
			\| '''Grafana Alloy'''
			\| `9100`
			\| For exposing Alloy's '''own internal metrics''' to be scraped by Prometheus. Its separate management UI runs on port `12345`.
	\|-		\|-
	\| '''Node Exporter'''		\| '''Node Exporter'''
	\| `~~9100~~`		\| `9101`
	\| Linux/Unix host metrics~~. The foundational Prometheus exporter~~.		\| Linux/Unix host metrics.
	\|-		\|-
	\| '''Windows Exporter'''		\| '''Windows Exporter'''
	\| `~~9101~~`		\| `9102`
	\| Windows host metrics.		\| Windows host metrics.
	\|-		\|-
	\| '''Blackbox Exporter'''		\| '''Blackbox Exporter'''
	\| `~~9102~~`		\| `9103`
	\| Probing endpoints (ICMP/HTTP/TCP) for availability.		\| Probing endpoints (ICMP/HTTP/TCP) for availability.
	\|-		\|-
	\| '''cAdvisor'''		\| '''cAdvisor'''
	\| `~~9103~~`		\| `9104`
	\| Container-level resource usage metrics.		\| Container-level resource usage metrics.
	\|-		\|-
	\| '''kube-state-metrics'''		\| '''kube-state-metrics'''
	\| `~~9104~~`		\| `9105`
	\| Kubernetes API object state metrics.		\| Kubernetes API object state metrics.
	\|-		\|-
	\| '''Proxmox VE Exporter'''		\| '''Proxmox VE Exporter'''
	\| `~~9105~~`		\| `9106`
	\| Proxmox hypervisor, VM, and container metrics.		\| Proxmox hypervisor, VM, and container metrics.
	\|-		\|-
	\| '''eBPF Exporters'''		\| '''eBPF Exporters'''
	\| `~~9106~~`		\| `9107`
	\| For advanced Linux kernel telemetry.		\| For advanced Linux kernel telemetry.
	\|-		\|-
	\| '''Process Exporter'''		\| '''Process Exporter'''
	\| `~~9107~~`		\| `9108`
	\| For detailed metrics on specific Linux processes.		\| For detailed metrics on specific Linux processes.
	\|}		\|}

Gyurci08 at 16:20, 27 August 2025

2025-08-27T16:20:29Z

← Older revision		Revision as of 16:20, 27 August 2025
Line 1:		Line 1:
	= Prometheus Exporter Port Allocation Standard =		= Prometheus Exporter Port Allocation Standard =

	This document defines the '''official internal standard''' for Prometheus exporter port assignments within our infrastructure. The primary goal is to create a cohesive, consistent, and maintainable port scheme that prevents conflicts ~~and~~ is easy to understand and extend.		This document defines the '''official internal standard''' for Prometheus exporter port assignments within our infrastructure. The primary goal is to create a cohesive, consistent, and maintainable port scheme that prevents conflicts, is easy to understand, and is simple to extend.

	== Guiding Principles ==		== Guiding Principles ==
Line 11:		Line 11:
	----		----

	== ~~Observability &~~ Core Infrastructure (9100-~~9119~~) ==		== Special Case: Grafana Alloy ==
	This block covers the foundational layer of our stack, from the ~~observability agent itself~~ to the ~~hosts and~~ orchestration platforms.		Grafana Alloy is our primary telemetry collector and is treated as a special case due to its unique role and well-known default port.

			* '''Role''': Alloy is configured to scrape other exporters on their assigned ports (defined below). It also receives OpenTelemetry data and tails log files.
			* '''Management UI Port''': The Alloy web UI for debugging and graph visualization will always run on its default port, '''`12345`''' [11].
			* '''Internal Metrics''': If Alloy is configured to expose its own internal metrics, it will be assigned a port from the standard block below, just like any other exporter.

			----

			== Core Infrastructure & Orchestration (9100-9109) ==
			This block covers the foundational layer of our stack, from the hosts to the orchestration platforms.

	{\| class="wikitable"		{\| class="wikitable"
Line 21:		Line 30:
	! Notes		! Notes
	\|-		\|-
	\| '''~~Grafana Alloy~~'''		\| '''Node Exporter'''
	\| `9100`		\| `9100`
	\| ~~For exposing Alloy's '''own internal~~ metrics~~'''~~. ~~Its management UI remains on port `12345`. Alloy scrapes other exporters on their respective ports below~~.		\| Linux/Unix host metrics. The foundational Prometheus exporter.
	\|-		\|-
	\| '''~~Node~~ Exporter'''		\| '''Windows Exporter'''
	\| `9101`		\| `9101`
	~~\| Linux/Unix host metrics.~~
	\|-
	~~\| '''Windows Exporter'''~~
	~~\| `9102`~~
	\| Windows host metrics.		\| Windows host metrics.
	\|-		\|-
	\| '''Blackbox Exporter'''		\| '''Blackbox Exporter'''
	\| `~~9103~~`		\| `9102`
	\| Probing endpoints (ICMP/HTTP/TCP) for availability.		\| Probing endpoints (ICMP/HTTP/TCP) for availability.
	\|-		\|-
	\| '''cAdvisor'''		\| '''cAdvisor'''
	\| `~~9104~~`		\| `9103`
	\| Container-level resource usage metrics.		\| Container-level resource usage metrics.
	\|-		\|-
	\| '''kube-state-metrics'''		\| '''kube-state-metrics'''
	\| `~~9105~~`		\| `9104`
	\| Kubernetes API object state metrics.		\| Kubernetes API object state metrics.
	\|-		\|-
	\| '''Proxmox VE Exporter'''		\| '''Proxmox VE Exporter'''
	\| `~~9106~~`		\| `9105`
	\| Proxmox hypervisor, VM, and container metrics.		\| Proxmox hypervisor, VM, and container metrics.
	\|-		\|-
	\| '''eBPF Exporters'''		\| '''eBPF Exporters'''
	\| `~~9107~~`		\| `9106`
	\| For advanced Linux kernel telemetry.		\| For advanced Linux kernel telemetry.
	\|-		\|-
	\| '''Process Exporter'''		\| '''Process Exporter'''
	\| `~~9108~~`		\| `9107`
	\| For detailed metrics on specific Linux processes.		\| For detailed metrics on specific Linux processes.
	\|}		\|}

Gyurci08 at 16:18, 27 August 2025

2025-08-27T16:18:21Z

Show changes

Gyurci08 at 16:15, 27 August 2025

2025-08-27T16:15:41Z

Show changes

Gyurci08 at 16:12, 27 August 2025

2025-08-27T16:12:30Z

← Older revision		Revision as of 16:12, 27 August 2025
Line 4:		Line 4:

	== Guiding Principles ==		== 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]~~.		* '''IANA Unofficial Ports''': The port range `9100-9999` is the community-accepted range for monitoring exporters. We will adhere to this where possible.
	* '''Consistency is Key''': When a de facto standard port exists (e.g., `9100` for `node_exporter`), we will use it.		* '''Consistency is Key''': When a de facto standard port exists (e.g., `9100` for `node_exporter`), we will use it.
	* '''Clarity Over Brevity''': For complex tools, a brief explanation is better than a single, potentially misleading port number.		* '''Clarity Over Brevity''': For complex tools, a brief explanation is better than a single, potentially misleading port number.

Gyurci08 at 16:12, 27 August 2025

2025-08-27T16:12:16Z

← Older revision		Revision as of 16:12, 27 August 2025
Line 5:		Line 5:
	== Guiding Principles ==		== 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].		* '''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]~~.		* '''Consistency is Key''': When a de facto standard port exists (e.g., `9100` for `node_exporter`), we will use it.
	* '''Clarity Over Brevity''': For complex tools, a brief explanation is better than a single, potentially misleading port number.		* '''Clarity Over Brevity''': For complex tools, a brief explanation is better than a single, potentially misleading port number.

Line 140:		Line 140:
	\|}		\|}
	-->		-->

	~~<!-- Add other categories as needed, such as "Cloud Services", "Networking", etc. -->~~

	[[Category:Prometheus]]		[[Category:Prometheus]]
	[[Category:Snippets & Notes]]		[[Category:Snippets & Notes]]

Gyurci08 at 16:11, 27 August 2025

2025-08-27T16:11:53Z

Show changes

Gyurci08 at 15:59, 27 August 2025

2025-08-27T15:59:07Z

Show changes

Gyurci08 at 15:53, 27 August 2025

2025-08-27T15:53:35Z

← Older revision		Revision as of 15:53, 27 August 2025
Line 1:		Line 1:
	[[Category:Prometheus]]		[[Category:Prometheus]]
			[[Category:Snippets & Notes]]

	{\| class="wikitable"		{\| class="wikitable"

Gyurci08 at 20:04, 1 August 2025

2025-08-01T20:04:04Z

Show changes