S
Supanote
Sign in Sign up
Logs & SRE · Zero Signup Required

Online Nginx Access & Error Log Analyzer

Paste raw /var/log/nginx/access.log or error.log lines to automatically highlight 4xx/5xx status spikes, isolate upstream gateway timeouts, detect accidental credential leaks, and share a clean diagnostic link with your team.

7 lines · 1296 B
Live Output Ready
1
203.0.113.42 - - [06/Nov/2026:14:21:08 +0000] "GET /api/v1/checkout HTTP/2.0" 200 1842 "https://app.example.com/cart" "Mozilla/5.0" rt=0.041 uct="0.004" urt="0.039"
2
198.51.100.17 - - [06/Nov/2026:14:21:11 +0000] "POST /api/v1/payments/charge HTTP/2.0" 504 569 "https://app.example.com/checkout" "Mozilla/5.0" rt=30.002 uct="0.003" urt="30.001"
3
2026/11/06 14:21:11 [error] 2841#2841: *99182 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 198.51.100.17, server: api.example.com, request: "POST /api/v1/payments/charge HTTP/2.0", upstream: "http://10.0.4.18:8080/api/v1/payments/charge"
4
192.0.2.88 - - [06/Nov/2026:14:21:14 +0000] "GET /api/v1/orders?limit=25 HTTP/2.0" 429 148 "-" "python-httpx/0.27.0" rt=0.002
5
2026/11/06 14:21:16 [warn] 2841#2841: *99204 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/4/01/0000000014 while reading upstream
6
203.0.113.99 - - [06/Nov/2026:14:21:19 +0000] "GET /healthz HTTP/1.1" 200 15 "-" "kube-probe/1.31" rt=0.001
7
2026/11/06 14:21:22 [error] 2842#2842: *99231 connect() failed (111: Connection refused) while connecting to upstream, client: 198.51.100.54, server: api.example.com, request: "GET /api/v1/inventory HTTP/2.0", upstream: "http://10.0.4.19:8080/api/v1/inventory"
Terminal / CI Pipe Equivalent
tail -n 200 /var/log/nginx/error.log | curl --data-binary @- https://supanote.app/paste

Pipe production Nginx logs directly from an SSH session into an unlisted diagnostic URL.

Capabilities & Guarantees

  • ✓ Automatic HTTP 2xx, 3xx, 4xx, and 5xx status code color badges
  • ✓ Severity filtering across ERROR, WARN, INFO, and upstream socket failures
  • ✓ Built-in heuristic detection for leaked Bearer tokens, cookies, and IPs
  • ✓ One-click unlisted or password-locked link creation for incident channels

Common Engineering Workflows

Debugging 502 Bad Gateway & 504 Gateway Timeouts

Correlate client-facing 502/504 access log lines with worker_connections, proxy_read_timeout, and upstream connection refused errors side by side.

Rate-Limit & Bot Traffic Triage (HTTP 429 / 403)

Spot aggressive scraper IPs, bursty API clients, and limit_req_zone rejections without spinning up a full ELK or Loki stack for a quick snippet.

Clean Incident Handoffs in Slack & PagerDuty

Replace truncated 200-line Slack code blocks with a single syntax-highlighted, severity-filtered Supanote URL that teammates can inspect immediately.

Technical Questions & Details

Does the Nginx Log Analyzer support both access.log and error.log lines together?

Yes. Supanote parses standard NCSA/combined Nginx access logs alongside Nginx worker [error], [warn], and [crit] lines in the same paste, extracting timestamps, status codes, IPv4 addresses, and severity badges.

Can I redact sensitive tokens or cookies before sharing an Nginx log?

Yes. The analyzer automatically scans pasted log lines for Authorization Bearer headers, session cookies, JWTs, and database URIs so you can sanitize sensitive credentials before generating a shareable link.

How do I pipe Nginx logs straight from a Linux server without opening a browser?

Run tail -n 200 /var/log/nginx/error.log | curl --data-binary @- https://supanote.app/paste from your terminal. Supanote auto-detects the log format and returns a clean URL immediately.

Explore Related Tools, Templates & Comparisons

Notification