Custom IDs & attributes
Respan indexes a few fields you can send with any request, so you can find every span that belongs to a ticket, an order, or a conversation. To tag the end user, use customer_identifier instead. See Users.
Send the fields
One request can carry all of them, plus customer_identifier.
Gateway
Tracing
client is the OpenAI client pointed at Respan, as in the Gateway quickstart. For other clients and headers, see Respan params.
Logging spans with the API? These are top-level span fields. See Create span.
Send custom_identifier as its own field. A custom_identifier key inside metadata is only a custom property, and doesn’t show up under Custom IDs.
Check a span
In Observability › Logs, click a span and open the Metadata tab. The identifiers are under Properties, and your metadata is under Custom properties.
Hover a row and click its filter icon to show only the spans with that value.
Filter Logs
In Observability › Logs:
- Custom ID or Thread ID: click More filters, pick the field, and enter the value.
- A custom property: click Custom property, search for the key, and pick a value.
- A whole conversation: switch the grouping from Spans to Threads. Each row is one
thread_identifier.
See Logs for filter groups and saved views.
Compare custom IDs
Switch to Custom IDs
Go to Observability › Users & identifiers and switch the grouping from Users to Custom IDs.

Each row is one custom_identifier, with its requests, tokens, cost, errors, and latency in the selected range. Click a metric card to chart the top five custom IDs by that metric.

