Prometheus & Kubernetes
Prometheus & Kubernetes Integration - Setup & Installation Docs | Middleware
Retrieve metrics from a Prometheus endpoint inside K8s.
Add Middleware Prometheus Integration as a sidecar container
To scrape the prometheus endpoint via Middleware Agent, You will have to add this sidecar container
in your pod:
Understanding Environment Variables
MW_TARGET : Specifies the target URL for the Middleware service. This URL defines the endpoint where your application should interact with the middleware.
Example Value : https://xxxxx.middleware.io:443
MW_API_KEY : Provides the API key required for authenticating with the Middleware service. Ensure the key is kept confidential and only shared with authorized users or services.
Example Value : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
PROMETHEUS_SCRAPE_CONFIG : Configures Prometheus scraping targets. This variable should be set in the format ‘job@address:port’, where ‘job’ represents the scraping job name, ‘address’ is the IP address or hostname, and ‘port’ is the port to scrape metrics from.
Example Value : job1@0.0.0.0:8889,job2@0.0.0.0:8890
Visualize Your Prometheus Metrics
You can now access this metrics data under our Dashboard builder
https://app.middleware.io/reports
- Create a new report
- ‘Add New Widget’ in the report.
- Select “prometheus” under the “Data Source” dropdown as shown in the screenshot below. You will be able to see a list of your metrics.

These metrics can be visualized using various widget types, such as Timeseries, Bar Chart, Pie Chart, and more.
Troubleshooting
Missing Integrations Menu
Missing Integrations Menu
Next Steps
- How to Create Alerts
- Dashboard Basics & Customization
- Custom Telemetry Ingestion
- Getting Started With Real User Monitoring (RUM)
- Data Ingestion APIs
- Configure OTel Collector Contrib