Dev
Generador de formatos de log
Used by developers, writers, and creators worldwide.
A log format generator gives you a clear specification and a matching sample line for a structured logging format, so your services log in a shape that humans and tools can both parse. Pick the format — newline-delimited JSON, logfmt key-value pairs, an nginx access log_format, or an Apache combined LogFormat — and name your service, and it returns the field list or directive plus a realistic sample line with a timestamp, level, trace id, duration, and status. SREs use it to standardise application logging or configure a web-server access log. It runs in your browser and generates instantly. Copy the format into your logger or web-server config, keep the field set consistent, and use the sample to verify your parser. Structured logs with a trace id and duration make logs searchable and let you tie a request together across services instead of grepping plain text.
Read the complete guide — 5 min read
Loading usage…
Free forever — no account required
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Pick the log format you want.
- Enter your service name.
- Click Generate to see the spec and a sample line.
- Copy it into your logger or web-server config.
Use Cases
- •Standardising application logs as structured JSON
- •Configuring an nginx or Apache access log format
- •Choosing between JSON and logfmt for readability
- •Including a trace id and duration in every log line
- •Giving a parser a known sample line to test against
Tips
- →Prefer structured logs so tools can index and search them.
- →Always include a trace id to correlate logs across services.
- →Log durations in milliseconds to spot slow requests.
- →Keep the field set identical across services for clean queries.
FAQ
JSON or logfmt — which should I use
JSON is best when a log pipeline ingests and indexes your logs, since every tool parses it. Logfmt is lighter and more readable for humans tailing a terminal. Both are structured, so either beats unstructured text for searching and alerting.
why include a trace id
A trace id ties together every log line for a single request, even as it crosses services. Without it, debugging a distributed flow means guessing which lines belong together; with it, you filter on one id and see the whole path.
where do the nginx and Apache formats go
The nginx log_format directive goes in the http block and is referenced by an access_log line, while the Apache LogFormat directive defines a nickname you reference in CustomLog. The samples show what each produces so you can confirm the layout.
You might also like
Popular tools from other categories that share themes with this one.