We’re excited to introduce our new NGINX log processor. Whether you're running NGINX in a standard deployment or using it as a Kubernetes Ingress Controller, Dash0 now handles it all. We automatically detect the format, extract structured data, and enrich it with semantic attributes that follow OpenTelemetry conventions—making it easier than ever to monitor and understand what’s happening in your services.
Automatic Detection & Parsing
We’ve built support for multiple common NGINX access log formats:
- Minimal Format – Essential request and response data
- Combined Format – Adds referer and user agent info
- Ingress Controller Format – Captures forwarded IPs
- Kubernetes Upstream Info – Includes upstream metrics and request IDs
You don’t need to write a single regex or modify your log format—just send your logs to Dash0 and we’ll handle the rest.
Semantic Enrichment Built In
We map NGINX variables to OpenTelemetry semantic conventions, giving you consistent and queryable log data across your entire stack.
Here are some examples what we extract and enrich:
Client Information:
$remote_addr→client.address
Request Attributes:
$request_method→http.request.method$request_uri→url.path$server_protocol→network.protocol.nameandnetwork.protocol.version$http_user_agent→user_agent.original
Response Data:
$status→http.response.status_code
This enrichment makes your logs more powerful, helping you correlate issues, create cleaner dashboards, and reduce your mean time to resolution.
Smarter Logs with Severity Detection
We’ve also introduced automatic severity inference based on HTTP status codes. Now your access logs are classified as:
INFO– for 1xx, 2xx, and 3xx responsesWARN– for 4xx client errorsERROR– for 5xx server errors
This means you can filter logs by severity level without having to configure anything manually.
It’s Available Now
This feature is now live for all Dash0 users. Just forward your NGINX access logs to us—no changes needed on your end. We’ll handle the parsing, structuring, and enrichment automatically.