Model Telemetry¶
Verlato emits model telemetry as realtime stderr activity for editor clients and, optionally, JSONL debug records for local investigation.
Controls¶
VERLATO_TRACE_MODEL_CALLS=1enables model lifecycle logs on stderr.VERLATO_TRACE_MODEL_PAYLOADS=1includes full prompt and response payload events.VERLATO_TRACE_MODEL_REASONING=1includes full provider-exposed reasoning text in collapsed details and streamed reasoning chunks.VERLATO_REDACT_MODEL_PAYLOADS=0disables payload redaction for deep local debugging. Redaction is on by default.VERLATO_MODEL_LOG_PATH=<path>appends JSONL debug records.- VS Code mirrors these with
verlato.telemetry.includePromptPayloads,verlato.telemetry.includeReasoningPayloads,verlato.telemetry.redactPayloads, andverlato.telemetry.debugModelLogPath.
Payload telemetry is off by default because prompts can include PR text and diff snippets. Reasoning payloads are separately off by default because provider-exposed reasoning can be large. Clients may still show reasoning_exposed and reasoning_chars without showing the reasoning text. When payloads are enabled, Verlato redacts common secret shapes by default and sets redacted=true on affected telemetry attributes.
Stderr Events¶
Human-readable lines use this prefix:
[verlato:model] <message>
Payload events also emit a structured companion line:
[verlato:model] json {"event":"prompt_preview","attributes":{"chars":123},"message":"...","payload":"..."}
Editor clients should coalesce stream_chunk events by request, task, and kind
before rendering. Verlato's VS Code view shows reasoning chunks as one live
reasoning block and content chunks as one live response block. Reasoning detail
is rendered collapsed by default when full reasoning payloads are enabled.
Fields:
event: stable snake_case event name.message: compact human-readable message.attributes: structured metadata for filtering and future export.payload: optional full text, emitted only when payload telemetry is enabled.attributes.redacted: whether the payload text was modified by redaction.
Current event names:
suggestion_plantarget_selectionevidence_builtevidence_detailprompt_builtprompt_budgetprompt_previewrequest_startedstream_chunkstream_completerequest_finishedresponse_detailresponse_previewreasoning_previewsuggestion_parsesuggestion_acceptsuggestion_rejectsuggestion_raw_responsesuggestion_decision
JSONL Debug Sink¶
Provider logs written by VERLATO_MODEL_LOG_PATH use an OpenTelemetry-style record shape with fields such as Timestamp, SeverityText, Body, Resource, InstrumentationScope, Attributes, and EventName.
CLI lifecycle events written to the same path use the lighter stderr event shape above. This keeps local debugging readable while leaving the provider boundary ready for JSON/OTLP export.
Export¶
Use verlato model-logs export --file <model-debug.jsonl> to normalize a debug JSONL file into a verlato.model_logs.v1 JSON document:
verlato model-logs export --file model-debug.jsonl --output model-export.json
Use --format jsonl to emit one normalized record per line, and --event <name> to filter to one or more event names. Export redacts likely secrets by default, even if older logs were captured before redaction existed. Set VERLATO_REDACT_MODEL_PAYLOADS=0 only when exporting raw local debugging data intentionally.