Skip to content

api-errors: the alert counts the server's failures, not callers told no - #12

Merged
aledbf merged 1 commit into
mainfrom
api-errors-server-failures
Nov 18, 2026
Merged

aledbf merged 1 commit into
mainfrom
api-errors-server-failures

Conversation

@aledbf

@aledbf aledbf commented Nov 18, 2026

Copy link
Copy Markdown
Member

For spin-stack/spin#1278: the High API Error Rate alert and the API error rate panels count only the server's failures (INTERNAL, UNAVAILABLE, UNKNOWN, DATA_LOSS, and DEADLINE_EXCEEDED on anything but WaitWorkspace and WaitSnapshot). NOT_FOUND, UNAUTHENTICATED, FAILED_PRECONDITION and the rest are the API answering.

The runbook says what is counted, renames the panel it points to (Answers other than OK), and drops the two fixes for answers the alert no longer counts. The spin PR bumps its runbooks pin to this commit.

🤖 Generated with Claude Code

The High API Error Rate alert now counts INTERNAL, UNAVAILABLE, UNKNOWN,
DATA_LOSS, and DEADLINE_EXCEEDED on anything but WaitWorkspace and
WaitSnapshot (spin-stack/spin#1278). The runbook says so, names the
codes it does not count, and drops the two fixes for answers it no
longer counts (a client looping on UNAUTHENTICATED, a CLI of another
release refused with FAILED_PRECONDITION).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@aledbf
aledbf merged commit 2f35224 into main Nov 18, 2026
1 check passed
@aledbf
aledbf deleted the api-errors-server-failures branch November 18, 2026 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant