Skip to content

fix(metrics): exclude BadRequestRockError from request.failure metrics (#1138)#1139

Open
jake11-oho wants to merge 1 commit into
alibaba:masterfrom
jake11-oho:worktree-bad-request-exception-change
Open

fix(metrics): exclude BadRequestRockError from request.failure metrics (#1138)#1139
jake11-oho wants to merge 1 commit into
alibaba:masterfrom
jake11-oho:worktree-bad-request-exception-change

Conversation

@jake11-oho

Copy link
Copy Markdown
Collaborator

Summary

  • Add request.client_error metric counter to separately track BadRequestRockError (client 4xxx errors)
  • Modify _record_metrics to route BadRequestRockError to .client_error instead of .failure
  • Server-side errors (InternalServerRockError, generic Exception, etc.) continue to go to .failure

fixes #1138

Test plan

  • test_record_metrics_bad_request_goes_to_client_error — verifies BadRequestRockError goes to .client_error, NOT .failure
  • test_record_metrics_server_error_goes_to_failure — verifies InternalServerRockError still goes to .failure
  • All 19 metrics decorator tests pass
  • All 36 related unit tests (sandbox manager, state machine, phase failure) pass

🤖 Generated with Claude Code

BadRequestRockError (client 4xxx errors) was being counted in request.failure
alongside server errors, polluting failure alerting. Route client errors to a
separate request.client_error counter so request.failure only reflects genuine
server-side failures.

fixes alibaba#1138

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.

fix(metrics): exclude BadRequestRockError from request.failure metrics

1 participant