René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"SoftwareApplication","@id":"https://www.evlog.dev/#identity","license":"https://github.com/evloghq/evlog/blob/main/LICENSE","author":{"@type":"Person","name":"HugoRCD","url":"https://hugorcd.com/"}}

{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"I already use pino. What actually changes?","acceptedAnswer":{"@type":"Answer","text":"evlog supplies a context accumulator and integrations that finish the request event. log.set() adds fields during the operation, and the emitted event carries its outcome and error together. Pino can also emit a completed object once, with accumulation managed by your application. createError() adds why and fix , and a catalog gives recurring failures a stable code. Call signatures, serializers, and output configuration need an explicit migration. See the comparison for your stack ."}},{"@type":"Question","name":"My app is already in production. Is it too late?","acceptedAnswer":{"@type":"Answer","text":"No, and you do not have to guess where to start. evlog map reads your source and scores every entry point on the context it will hand you when it breaks, then names the ones to fix first. It needs no traffic, no agent, and no deploy, so you get that list before the next incident instead of during it. Day one or year three, the work is the same list. See adding it to an app already in production ."}},{"@type":"Question","name":"Do I have to change where my logs go?","acceptedAnswer":{"@type":"Answer","text":"No, and you keep the platform you already pay for. evlog produces the events, a drain ships them: Axiom, Datadog, Sentry, Better Stack, PostHog, Loki, ClickHouse, OTLP, or the filesystem. Changing provider is a drain swap, not an architecture change, because your handlers never name a destination. If you are building the platform rather than buying one, that same pipeline is where you plug in. See how a drain keeps the destination out of your code ."}},{"@type":"Question","name":"Will it cost me more to ship these logs?","acceptedAnswer":{"@type":"Answer","text":"It usually costs less. One request leaves one event instead of four lines, which measures 56% fewer bytes and 75% fewer events on the checkout shape in the log cost guide , because the level, timestamp, host and request bindings stop repeating on every line. Which of those two numbers moves your bill depends on your provider: most charge per GB ingested, so you save on bytes, while a provider that also bills per million events indexed rewards the event count instead. Then sampling drops what you were never going to read and force-keeps errors and slow requests. Price it against your own traffic on which number moves your bill ."}},{"@type":"Question","name":"How much work is it to adopt?","acceptedAnswer":{"@type":"Answer","text":"You migrate one handler at a time. Two calls are worth learning: log.set() , which adds context to the event in flight, and createError() , which attaches a why and a fix to an error instead of a bare stack. See how much of this you need on day one , or what evlog is if you want the shape before the code."}},{"@type":"Question","name":"What does it cost at runtime?","acceptedAnswer":{"@type":"Answer","text":"The core package has zero runtime dependencies . Execution cost depends on context size, redaction, output, and delivery. A silent construction benchmark excludes console serialization and remote export, so it cannot establish a fixed cost per production request. Follow what it costs on one real request to measure the complete path on your runtime."}}]}

{"@context":"https://schema.org","@graph":[{"@id":"https://www.evlog.dev/#website","@type":"WebSite","description":"Digging through logs is not observability. It's hope. evlog is a TypeScript logger: structured logs, wide events and actionable errors in one API.","inLanguage":"en","name":"evlog","url":"https://www.evlog.dev/"},{"@id":"https://www.evlog.dev#webpage","@type":"WebPage","description":"Digging through logs is not observability. It's hope. evlog is a TypeScript logger: structured logs, wide events and actionable errors in one API.","name":"evlog — TypeScript logger for wide events & structured logs","url":"https://www.evlog.dev","isPartOf":{"@id":"https://www.evlog.dev/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://www.evlog.dev"]}]},{"@id":"https://www.evlog.dev#/schema/software-application/1","@type":"SoftwareApplication","applicationCategory":"DeveloperApplication","description":"Digging through logs is not observability. It's hope. evlog is a TypeScript logger: structured logs, wide events and actionable errors in one API.","name":"evlog","operatingSystem":"Node.js, Bun, Deno, Cloudflare Workers, all major browsers","offers":{"@type":"Offer","availability":"https://schema.org/InStock","price":0,"priceCurrency":"USD","priceValidUntil":"2027-12-30T00:00:00.000Z"},"sameAs":["https://github.com/evloghq/evlog","https://www.npmjs.com/package/evlog","https://x.com/hugorcd"]}]}