Krisztian F 645be8957c (otel): split infra vs. workload faults (#1445) ...

`ate.failure.reason` only ever named infrastructure faults, and the
crash log didn't say which actor crashed.

This PR adds the following:

- **`ate.failure.domain`** (`infrastructure` / `workload` / `unknown`)
is available next to every `ate.failure.reason`. It's a strict function
of the reason so it costs no series, but it's *emitted* rather than
derived downstream, so a component ahead of ateapi can report a reason
this build rejects, which collapses to `UNKNOWN`, and a consumer
matching on reason names would file every one of those as infra.
`UNKNOWN` now reports `unknown`, not `infrastructure`.
- **`Actor crashed`** record from ateapi, with full identity including
the uid, via a helper both crash sites share. It sits under the same
guard as the counter so the two can't disagree on how many crashes
happened. The counter is barred from carrying actor identity, so this
record is the only way to attribute a crash to one agent.
- **`WORKLOAD_NOT_READY`** on the readyz deadline, as the first
workload-domain reason. Deadline branch only: a cancellation is ateom
draining, not the actor failing.

Tested locally:
```
desc = WORKLOAD_NOT_READY: readyz for "counter" never returned 200 within 5s
```

- [x] Tests pass
- [x] Appropriate changes to documentation are included in the PR

2026-09-03 16:53:27 -04:00

..

ateerrors_test.go

feat: Add control plane telemetry - actor crashes counter and operation labels (#642)

2026-08-05 16:31:43 -04:00

ateerrors.go

(otel): split infra vs. workload faults (#1445)

2026-09-03 16:53:27 -04:00