Client telemetry
Since 2026.11.9 Quasar receives the OpenTelemetry of coding clients at /api/otlp/v1/logs and /api/otlp/v1/traces, over HTTP, in JSON or protobuf, authenticated by an ingest key.
-
What it keeps:
- for each call the client made to a model: the time, the conversation, the model and the tokens by class;
- since 2026.11.10, each turn's span, its client, and the project label its repository declares;
- each call the agent made to Quasar's own tools: its tool, its time and how it ended. Of its arguments, Quasar keeps only the issue or project named, and of any other tool, nothing.
Never the text of a prompt or of an answer. A record dated more than seven days back, or more than five minutes ahead, is refused.
-
When a turn is proposed (since 2026.11.16). It is proposed in the same step that receives the client's signal that the turn ended (the span that wraps it, or Claude Code's
Stophook), so nothing waits for a timer. A client that never sends that signal has its turns proposed by a background job after ten minutes of silence, and a turn never closed after a day. -
A client Quasar cannot read yet: its records are kept raw for seven days, so that a driver can be written from them, then deleted.
-
Telemetry that does not arrive (since 2026.11.13) is noticed from the agent's calls to Quasar's own tools, which Quasar already records: nothing more is collected for it. The person is told by the notification Telemetry not arriving, at most once per key and day.
-
The model calls, and the turns with their calls to Quasar, are kept 400 days, whatever the organization's trash retention. They belong to the person whose key sent them and are part of that person's data export. A confirmed work log keeps its own copy of the usage it was given, so it outlives them.
-
The direction is the client's. The client calls Quasar, as a webhook does; Quasar holds no credential of the client's and reads nothing on the person's machine.