Log & observability tools
Debugging from logs means reading formats that were never meant for humans: an Nginx access log line with a custom log_format, an RFC 5424 syslog message with its PRI value encoding facility and severity together, a stack trace pasted from a language you don't normally read, or a traceparent header you need to confirm is actually well-formed before you trust the trace it names. These tools parse that raw text into fields you can scan.
Match the source to the parser: the Access Log Parser reads Nginx and Apache logs including custom formats, the AWS Log Parser auto-detects CloudFront and ALB log layouts, and the Syslog Parser splits both RFC 3164 and RFC 5424 messages into PRI, facility and severity. For debugging rather than ingestion, the Stack Trace Formatter organizes frames from multiple languages, the Traceparent Parser validates W3C Trace Context headers, and the PromQL formatter checks PromQL syntax and tests vector selectors without a running Prometheus instance.
8 tools
Parse logs into fields
-
Access Log Parser
Parse Nginx and Apache access logs with custom format support
-
AWS Log Parser
Analyze CloudFront and ALB access logs with auto-detected formats
-
Syslog Parser
Split RFC 3164 and RFC 5424 syslog with PRI, facility and severity
-
Log Viewer
Format and filter JSON, logfmt, Kubernetes and Docker logs as tables
Debug traces and queries
-
Stack Trace Formatter
Parse and organize stack traces from multiple languages with frames
-
Traceparent Parser
Decode traceparent headers and validate W3C Trace Context format
-
PromQL formatter
Check PromQL syntax and test vector selectors against pasted metrics without live Prometheus
-
Unix timestamp converter
Convert between Unix timestamps and dates across units and timezones
Logs & Observability tools FAQ
The PRI value at the start of a syslog message is a single number that encodes both facility and severity packed together as facility times 8 plus severity. The Syslog Parser splits RFC 3164 and RFC 5424 messages apart and shows the decoded facility and severity directly.
A valid W3C Trace Context traceparent header has a fixed version, a 16-byte trace ID, an 8-byte parent ID and flags, each in a specific hex format, and a single wrong-length field breaks propagation. The Traceparent Parser decodes a header and validates it against the W3C Trace Context format.
Yes, syntax and vector selector logic don't need a live metrics backend to check. The PromQL formatter checks PromQL syntax and lets you test vector selectors locally, which catches errors before you point the query at a real Prometheus server.