Last9
last9.io › blog › prometheus-port-configuration
Prometheus Port Configuration: Defaults and Setup (2026) | Last9
March 12, 2025 - The iptables command shows if there are explicit rules affecting port 9090, telnet tests basic TCP connectivity, and traceroute with the -T and -p flags show where along the network path TCP connections to port 9090 might be failing.
Prometheus
prometheus.io › docs › instrumenting › exporters
Exporters and integrations | Prometheus
Commonly, those exporters are hosted outside of the Prometheus GitHub organization. The exporter default port wiki page has become another catalog of exporters, and may include exporters not listed here due to overlapping functionality or still being in development.
Default prometheus exporter port for rtrtr
Prometheus maintains a list of allocations of default ports for exporters, and rtrtr has been added to the list as port 9810. This could be reflected as a recommendation or a default in rtrtr.conf.... More on github.com
system - How to config default port of Node Exporter - Stack Overflow
ExecStart=/usr/local/bin/node_exporter --web.listen-address=:[custum port] ... Sign up to request clarification or add additional context in comments. ... The file should be like /usr/lib/systemd/system/prometheus-node-exporter.service 2026-04-24T13:07:45.44Z+00:00 More on stackoverflow.com
Wiki page with default port allocation of prometheus exporters was overwritten
What did you do? I allocated the port 9641 for my prometheus exporter mqtt2prometheus. This was done in the commit/revision 60c661b7a1d662b18a6da2c11f2de1392306edd0 (Tue Jun 9 16:12:24 2020) of the wiki page. What did you expect to see? ... More on github.com
docker - How to Change Port Number in cadvisor and node-exporter of Prometheus Monitoring - Stack Overflow
Below is the showing in prometheus URL when i click on target. cadvisor (0/1 up) and node-exporter (0/1 up) are showing in Prometheus URL Here is the my filename.yml file version: '3.2' services: More on stackoverflow.com
21:11
Prometheus SNMP Exporter: Network Monitoring Tutorial! - YouTube
05:34
Exporters in Prometheus - YouTube
Monitoring Linux Host Metrics with Prometheus | Node ...
21:12
How to Build Custom Prometheus Exporter? (Step-by-Step - Real-world ...
23:05
Prometheus Monitoring - Steps to monitor third-party apps using ...
04:56
Monitoring Networks with Prometheus and the SNMP exporter: A Brief ...
Prometheus
prometheus.io › docs › instrumenting › writing_exporters
Writing exporters | Prometheus
This is a registry to make our users’ lives a little easier, not a commitment to develop particular exporters. For exporters for internal applications we recommend using ports outside of the range of default port allocations.
SigNoz
signoz.io › guides › how to change prometheus port - a step-by-step guide
How to Change Prometheus Port - A Step-by-Step Guide | SigNoz
December 5, 2024 - When Prometheus or its monitored services operate on non-default ports, you need to adjust the scrape_configs section of the prometheus.yml file to ensure accurate · Open prometheus.yml and locate the scrape_configs section. ... scrape_configs: - job_name: 'node_exporter' static_configs: - targets: ['localhost:9100'] - job_name: 'custom_service' static_configs: - targets: ['service-host:8000']
Netapp
netapp.github.io › harvest › 23.08 › prometheus-exporter
Prometheus Exporter - Harvest
Admin: httpsd: listen: :8887 Exporters: prometheus-r: exporter: Prometheus port_range: 13000-13999 Defaults: collectors: - Zapi - ZapiPerf use_insecure_tls: false auth_style: password username: admin password: pass exporters: - prometheus-r Pollers: umeng_aff300: datacenter: meg addr: 10.193.48.11 ...
OpenTelemetry
opentelemetry.io › docs › specs › otel › metrics › sdk_exporters › prometheus
Metrics Exporter - Prometheus | OpenTelemetry
The option MAY be named port, and MUST be 9464 by default. ... A Prometheus Exporter SHOULD support a configuration option to set the MetricReader default aggregation as a function of instrument kind.
Top answer 1 of 2
9
To change port number, this is the example for cadvisor and node exporter
version: '3.2'
services:
cadvisor:
image: google/cadvisor:latest
ports:
- 9092:9092
...
command:
- '-port=9092'
...
node-exporter:
image: prom/node-exporter:latest
...
ports:
- 9091:9091
command:
# To specify port in node-exporter colon is required
- '--web.listen-address=:9091'
...
2 of 2
0
In your docker configuration file, you're not mapping the right port on those three services :
- node_exporter
- cadvisor
- karma-alert-dashboard
You need to map the ports that are exposed by those docker image.
For example, for the node_exporter, if you want to access it on port 9091 of your VM, you'll have something like this :
ports:
- 9091:9100 # node_exporter works on port 9100 by default
If you want to know wich port are exposed by those images, you can just have a look at the github documentation of each project or do a docker image inspect your_image
client_java
prometheus.github.io › client_java › config › config
Config | client_java
The property above changes the port for the HTTPServer exporter to 9401. Properties file: Add the line above to the properties file. System properties: Use the command line parameter -Dio.prometheus.exporter.http_server.port=9401 when starting your application.
GitHub
github.com › prometheus-community › windows_exporter
GitHub - prometheus-community/windows_exporter: Prometheus exporter for Windows machines · GitHub
This can be useful for having different Prometheus servers collect specific metrics from nodes. windows_exporter accepts flags to configure certain behaviours. The ones configuring the global behaviour of the exporter are listed below, while collector-specific ones are documented in the respective collector documentation above. Flag · Description · Default value · --web.listen-address · host:port for exporter.
Author: prometheus-community