You can't debug what you didn't log. Polylane finds your blind spots and closes them.
Join the waitlist Observability improvements for #218 polylane +22 −2
Requests do not produce one context-rich event
3 affected routes · found by the scan after the last sync
server/api/checkout.post.ts mirrors your existing OpenTelemetry setup; no new dependencies
export default defineEventHandler(async (event) => {
const body = await readBody(event);
- const order = await createOrder(body);
- return { orderId: order.id };
+ return tracer.startActiveSpan("checkout", async (span) => {
+ const canonical: Record<string, unknown> = {
+ route: "checkout",
+ requestId: event.context.requestId,
+ cartId: body.cartId,
+ traceId: span.spanContext().traceId,
+ };
+ try {
+ const order = await createOrder(body);
+ span.setAttributes({ "order.id": order.id, "order.amount_cents": order.amountCents });
+ Object.assign(canonical, { orderId: order.id, amountCents: order.amountCents, outcome: "ok" });
+ return { orderId: order.id };
+ } catch (err) {
+ span.recordException(err);
+ span.setStatus({ code: SpanStatusCode.ERROR });
+ canonical.outcome = "error";
+ throw err;
+ } finally {
+ span.end();
+ emitCanonicalLogLine(canonical);
+ }
+ });
});
Opened against the pull request's own branch, so it can merge before the branch does.
You discover the missing log line mid-incident. Polylane finds it first.
-
It reads your routes
Which ones log, which trace, which swallow errors. The gaps become findings, each with evidence and a fix.
-
Your stack, not a new one
Your logger, your OpenTelemetry setup, your conventions. No new dependencies, never a logged secret.
-
Fixes as pull requests
The first one arrives when you connect. Later ones ride along with code reviews, against your branch.
-
It knows when to stop
Already solid? It says so and stops.