Archive / Topic
#observability
5 posts, newest first
Separate request identity from attempt identity
Retries stay auditable when the customer's command keeps one identity and every execution receives another
Queue depth hides the oldest promise
A backlog count can look healthy while one customer's message has been waiting far beyond the delivery contract
Admin detail should fail closed
Broad operational visibility can be useful to many users, but infrastructure detail should disappear by default the moment privilege is unclear
When the error message lies about the failure
A production incident gets slower and riskier when the recorded failure names the wrong boundary
Investigation starts with the records you keep
Audit and observability are data models first, dashboards second
Often tagged alongside observability