Send traces
Send a team's runs as OpenTelemetry traces to Laminar or another collector you already use.
If you already watch your AI work in an observability tool, Sculptured can send each run there as one trace. Laminar is built in; any collector that takes OTLP over HTTP (Langfuse, Datadog, Honeycomb, your company's own) works the same way. The board stays the main view: traces are a copy for the tools you already have.
Sending is off until you turn it on, team by team.
Turn it on
- Open the team's settingsOpen the team, then Settings → More settings → Send traces.
- Choose whereLeave Send to on Laminar, or choose Another OTLP/HTTP collector and give its address (it usually ends in
/v1/traces). - Add the keyPaste the project API key from your tool. Sculptured's server keeps it and sends it only to that address, as
authorization: Bearer <key>. It is never shown again; the page only says A key is saved. - Choose what to sendTimings, tokens and costs (the default), or Also prompts and outputs.
- SaveTick Send this team's runs as traces and choose Save. The team's latest run (one going now, or the last one if it has finished) is sent from its start, then each new run as it goes.
What a trace holds
| Span | What it carries |
|---|---|
| run | The team. Events for budget changes, questions asked and answered, hand-overs, suspected stalls and checks. |
| agent | One per session of an agent: its name, Claude Code or Codex, and the computer. |
| turn | The model as observed, tokens in and out (with cache reads and writes), the cost when it is priced, and how the turn ended. Marked as an LLM span. |
| tool | The tool's name and whether it failed, under its turn (or the call that started it). |
A turn or tool goes when it ends, an agent span when its session ends, and the run span once the run has stopped and its agents' sessions have ended (or a minute after the stop). If you start the team again before that, the earlier run is still sent whole. A session that never reported its end is closed at the end of the run and marked incomplete.
Timings, tokens and costs sends no text from your work, but it does name things: the team's name and id, each agent's name and id, the computer's id, the models, the tools used, and the reasons given for budget changes and suspected stalls.
Also prompts and outputs adds, each cut to 4 KB: every turn's input message and the agent's reply, and every tool call's input and output. Tool inputs and outputs include file contents, commands and what they printed. Choose it only if the tool you send to may hold all of that. Switching back to timings applies at once, also to a run that is going.
When a send fails
A failed send is tried again every few seconds with the same spans, so nothing is lost while the collector is down. The settings show why the last send failed (for example, the key was refused). If the collector stays unreachable for a long time, Sculptured keeps the newest 20,000 spans and says how many it dropped.
Addresses you can use
- On your own computer: any
https://address, orhttp://to this computer (localhost,127.0.0.1) for a collector you run locally. - In the hosted app: a public
https://address only. The server will not send to itself or its own network.
Redirects are not followed, so the key reaches only the address you entered. If you change the address, enter the key again: a saved key is never sent to a different address.