Traces reference
Ingest and identity
Section titled “Ingest and identity”Use OTLP HTTP protobuf or JSON at https://otlp.siteqwality.com/v1/traces. Set service/environment/version resource attributes. Trace IDs are 32 hexadecimal characters and span IDs 16, and all-zero IDs are invalid. Parent IDs, span kind, start/end time, events and links describe the actual recorded graph. The receiver does not infer missing spans.
OTLP over gRPC is not available yet. Platform guides include SDK setup and exporter flushing.
API reference
Section titled “API reference”| API-relative path | Method | Purpose |
|---|---|---|
/traces/ | POST / GET | Span/trace search with a versioned query. |
/traces/ | POST | Detail for trace ID and bounded range. |
/traces/ | GET | Retained spans and trace summary. |
/traces/ | GET | Span detail, events, links and attributes. |
/traces/ | GET | Recorded log correlation. |
/traces/ | GET | RED series for selected scope. |
/traces/ | GET | Endpoint/service ranking. |
/traces/ | GET | Duration distribution. |
/traces/ | GET | Matching spans per time bucket, with error counting the spans a status:error filter matches. |
/traces/ | POST | Bounded period comparison. |
Use https://api.siteqwality.com and read credentials. Preserve service/environment/time restrictions when following a link. A span query uses signal: "spans"; a supported trace summary query uses "traces". Use typed query examples.
Explorer interpretation
Section titled “Explorer interpretation”Open a trace for waterfall, critical path, span events/links and correlated data. Timing offsets and durations are nanosecond strings; converting them to a floating point Number too early loses precision. The critical path describes recorded timing and does not prove causality for an unrecorded dependency. Incomplete/skeleton/truncated traces are labeled; do not assume they represent every operation in the request.
Service and endpoint RED uses weighted received spans and reports estimated and quality state; an upstream head sampler has already removed some requests. Percentiles are approximate. See the sampling guide and Services.
Traces have their own allowance and retention. Logs need matching trace IDs to correlate, and browser propagation is opt-in; see correlation and access/exports.