Changelog

Labels, Metadata & Custom Log Events for Traces

Tag individual requests with labels, attach key-value metadata, log custom events into traces, and inspect traces in a dedicated detail view.

Traces just got a lot more useful. Four additions ship today:

Labels — Tag individual requests within a trace so you can see at a glance what each step does. Set a label globally with grepture.setLabel("extract-facts") or per-request via FetchOptions. Labels appear as badges in the trace timeline.

Metadata — Attach arbitrary key-value tags to requests (grepture.setMetadata({ userId: "u_123", environment: "prod" })). Metadata is visible in the request detail panel and can be set globally or per-request, with per-request values merging into the defaults.

Custom log events — Call grepture.log("cache-hit", { key: "embedding-abc" }) to log non-AI events directly into a trace. Log events appear inline in the trace timeline with expandable data and metadata. They are excluded from request counts and cost calculations.

Trace detail page — Every trace now has a dedicated page at /traffic-log/traces/<trace-id> with a shareable URL. The detail view shows each request as a collapsible panel with the full conversation (system prompt, user messages, assistant response) rendered inline — no need to click into each request individually.