Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

600 Operator Error status code #3450

Open
steve-chavez opened this issue Apr 24, 2024 · 0 comments
Open

600 Operator Error status code #3450

steve-chavez opened this issue Apr 24, 2024 · 0 comments
Labels
http http compliance idea Needs of discussion to become an enhancement, not ready for implementation observability

Comments

@steve-chavez
Copy link
Member

Problem

There are errors that are a clear operator error, such as PGRST121. Yet, these errors are mapped to a 500 status, which is a server error.

This is a problem for metrics because 5xx would be considered as PostgREST failures.

Solution

Map these errors to a custom status code 600 Operator Error.

Previously discussed on https://github.com/PostgREST/postgrest/pull/3423/files#r1576717938
@steve-chavez steve-chavez added http http compliance idea Needs of discussion to become an enhancement, not ready for implementation observability labels Apr 24, 2024
@steve-chavez steve-chavez mentioned this issue Apr 24, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
http http compliance idea Needs of discussion to become an enhancement, not ready for implementation observability
Milestone
No milestone
Development

No branches or pull requests
1 participant
@steve-chavez