Client diagnostic events
The generated ErrorCode API reference tracks the runtime’s current client event definitions. The error-code source on the main branch shows definitions under active development. Preserve structured EventId, category, exception, trace ID, and span ID fields in your log backend.
Search for the structured event ID in ErrorCode, then route by its category, exception, and surrounding symptoms:
| Diagnostic area | Remedy |
|---|---|
| Gateway discovery, connection, TLS, or reconnect | Connection and gateway failures |
| Request timeout or latency | Request timeouts |
| Silo unavailable or message rejected | Silo unavailable or message rejected |
| Gateway busy, load shedding, or rejection | Gateway or cluster overload |
| Serialization or codec | Serialization failures after a version change |
Base alerts on sustained service symptoms correlated with event IDs and runtime signals. Follow Interpret Orleans observability signals.