Integration · Web & proxy
Nginx
Active connections, RPS, upstream health, status codes.
What gets collected
stub_status plus log tailing to parse status codes. Virtual hosts are tracked via a server_name label.
Requirements
- ✓stub_status module
- ✓access_log JSON format
- ✓server_name label
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
nginx.connections.activenginx.requests.rpsnginx.upstream.healthnginx.status.5xxnginx.status.4xxSetup steps
- 1Enable stub_status in nginx.conf
- 2access_log in JSON format for the log
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
Nginx
Frequently asked questions
- What does Unimoni collect from Nginx?
- Active connections, RPS, upstream health, status codes. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across Nginx and everything else in one place.
- How long does it take to connect Nginx?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the Nginx integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is Nginx monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.