Usage API
Telemetry capture and the span engine behind Flow Intelligence.
For concepts and configuration see the block documentation.
Surfaces
Section titled “Surfaces”| Surface | Purpose |
|---|---|
capture | Ingest events |
definitions | Declare and manage event definitions and spans |
recompute | Re-materialise spans after a definition changes |
query | Trend and cohort-contrast aggregation |
recompute is the one with operational consequence: change a span definition without it and
the trend shows a discontinuity at the moment of the change, which reads as a change in the
process rather than in the measurement.
Tenancy
Section titled “Tenancy”Every request carries the platform tenancy headers — X-Kis-Tenant, X-Kis-Product and
X-Kis-Environment. Telemetry is stored per tenant.
Errors
Section titled “Errors”Errors use the platform’s structured error body: a stable code, a human-readable message, and the request id to correlate against logs and audit.