No builds are showing up

Telemetry fails quietly, on purpose

A build must never fail because the telemetry backend was unreachable or refused it. So every failure here looks the same from the pipeline: a green build with no spans. The job log is where the answer is.

Check in this order

1. Is the account enrolled? An unapproved request means the exchange returns 403. The job log says exchange refused.
2. Is the audience exactly kaniko-telemetry? A token minted for any other audience is rejected, which is what stops one minted for a cloud deployment being replayed here.
3. Is the endpoint the full path, ending /oidc/v1/traces? kaniko only appends /v1/traces to an endpoint that has no path of its own.
4. Is the kaniko version recent enough to emit spans at all? Releases before the instrumentation landed emit nothing, whatever you configure.

A build that stops halfway

A trace with instruction spans but no completed root span shows as a crashed build, not as missing data. If a build was killed — an out-of-memory runner is the usual cause — that is what you are looking at.

The same shape appears if the ingest token expired mid-build, so a long build that reads as crashed is worth checking against the token's lifetime.