Whether a project has ever received at least one trace span.
Changed onA pure existence check for onboarding/setup UI (e.g. "has this project set up OpenTelemetry yet?"). Deliberately not /otel/trace-summaries with limit=1: that endpoint aggregates by trace (GROUP BY trace_id, argMax) and, without a time bound, that aggregation runs over every span the project has ever ingested. This endpoint answers the same yes/no question in O(1) — see OtelStorage::has_traces.
Request
- Base URL: /api (relative, and the document was published on a file host, not at the API’s origin)
- URL: /api/otel/has-traces/{project_id}
- Auth: HTTP bearer
Path parameters
Project ID
Response
Trace existence check
Changes
- info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status
- info
- warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status
- warning