Reference
Reference
Every option, every number, and every comparison, in one place. Start here when you know what evlog does and need the exact value.
The rest of the docs teach evlog. This section answers the questions you arrive with a value in mind for: what is this option called, what does it default to, how much does it cost, and how does it compare.
What are you looking for?
| You want to know… | Read |
|---|---|
| What an option is called, what it defaults to, and which surface it belongs to | Configuration |
| How much CPU and how many bytes an event costs, and where evlog loses | Performance |
| What your bill does when one request leaves one event instead of four lines | Log cost |
| How evlog differs from pino, winston and consola, gaps included | evlog vs other loggers |
| Dedicated comparison pages, starting with pino, OpenTelemetry and LogTape | evlog vs Pino, evlog vs OpenTelemetry and evlog vs LogTape |
| What to log, what never to log, and how to keep an event useful under redaction | Best practices |
| What the Vite plugin strips from a production bundle and how to configure it | Vite plugin |
| How to hand your coding agent the evlog conventions | Agent skills |
The three numbers worth knowing
Each one is measured on the same checkout request, and each page shows the run behind it.
- Measure the configuration you deploy. Performance separates construction, serialization, and delivery costs and documents the limits of the comparison suite.
- 56% fewer bytes and 75% fewer events than four log lines carrying the same request. Log cost prices that against your own traffic.
- ~6.3 kB gzip and zero runtime dependencies, so there is no tree to audit before you can log.