Prometheus exporter in Nginx - Step-by-Step Execution

Process Flow - Prometheus exporter

Start Nginx with Exporter Module

↓

Nginx collects metrics

↓

Exporter exposes metrics at /metrics

↓

Prometheus scrapes /metrics endpoint

↓

Prometheus stores and visualizes metrics

↓

End

Nginx runs with an exporter module that collects metrics and exposes them at a URL. Prometheus regularly fetches these metrics to monitor Nginx.

Execution Sample

Nginx

location /metrics {
    stub_status;
    access_log off;
    allow 127.0.0.1;
    deny all;
}

Nginx configuration snippet exposing metrics at /metrics for Prometheus to scrape.

Process Table

Step	Action	Nginx State	Exporter Output	Prometheus Action
1	Nginx starts with /metrics location configured	Running with stub_status enabled	No metrics yet	No scrape yet
2	Nginx receives HTTP request at /metrics	Running	Generates current metrics snapshot	Receives metrics data
3	Prometheus scrapes /metrics endpoint	Running	Serves metrics text format	Stores metrics in time series database
4	Prometheus waits until next scrape interval	Running	Metrics updated continuously	Prepares for next scrape
5	Prometheus scrapes again	Running	New metrics snapshot served	Updates stored metrics
6	Monitoring dashboards update	Running	Metrics available	Visualizes Nginx performance
7	Nginx stops or exporter disabled	Stopped or no metrics	No metrics served	Scrape fails or stops

💡 Nginx stops or exporter disabled, so metrics are no longer served and Prometheus scraping ends.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	Final
Nginx State	Starting	Running	Running	Running	Stopped or Running
Exporter Output	None	Metrics snapshot	Metrics served	Updated metrics	None or Metrics
Prometheus Action	Idle	Scraping	Storing metrics	Updating metrics	Stopped or Visualizing

Key Moments - 3 Insights

Why does Prometheus need the /metrics endpoint in Nginx?

Prometheus scrapes data by requesting /metrics. Without this endpoint, Prometheus cannot collect Nginx metrics. See execution_table step 2 and 3.

What happens if Nginx stops serving /metrics?

Prometheus scraping fails and monitoring stops. This is shown in execution_table step 7 where no metrics are served.

Why is access restricted to 127.0.0.1 in the config?

To secure metrics so only local Prometheus can access them, preventing unauthorized access. This is part of the configuration in execution_sample.

Visual Quiz - 3 Questions

Look at the execution_table, what is the Exporter Output at Step 3?

A Serves metrics text format

B No metrics yet

C Generates current metrics snapshot

D No metrics served

💡 Hint

Check the Exporter Output column at Step 3 in the execution_table.

At which step does Prometheus first store metrics data?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the Prometheus Action column in the execution_table for when storing starts.

If the allow 127.0.0.1; line is removed from the config, what changes in the execution?

A Prometheus cannot scrape metrics

B Metrics become accessible from any IP

C Nginx stops serving metrics

D Exporter output stops updating

💡 Hint

Refer to the variable_tracker and key_moments about access control in the config.

Concept Snapshot

Prometheus exporter in Nginx:
- Configure /metrics location with stub_status
- Restrict access (e.g., allow 127.0.0.1)
- Prometheus scrapes /metrics regularly
- Metrics served in text format
- Prometheus stores and visualizes metrics
- Exporter must run for monitoring to work

Full Transcript

This visual execution shows how Nginx acts as a Prometheus exporter by exposing metrics at the /metrics endpoint. Nginx starts with the stub_status module enabled and configured to serve metrics only to allowed IPs like 127.0.0.1. When Prometheus scrapes the /metrics URL, Nginx generates a current snapshot of metrics and serves them in a text format. Prometheus stores these metrics in its time series database and updates them on each scrape interval. If Nginx stops or the exporter is disabled, metrics are no longer served and Prometheus scraping fails. Access control in the configuration ensures only authorized clients can get metrics. This step-by-step trace helps beginners understand the flow from Nginx metrics exposure to Prometheus monitoring.