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

Log all 500 errors by default #2232

Closed
EricWittmann opened this issue Feb 3, 2022 · 1 comment · Fixed by #2315
Closed

Log all 500 errors by default #2232

EricWittmann opened this issue Feb 3, 2022 · 1 comment · Fixed by #2315
Assignees
@EricWittmann
Labels
component/registry priority/high type/enhancement New feature or request

Comments

@EricWittmann
Copy link
Member

No description provided.

@EricWittmann EricWittmann self-assigned this Feb 3, 2022
@EricWittmann EricWittmann added the type/enhancement New feature or request label Feb 3, 2022
@jsenko
Copy link
Member

jsenko commented Feb 23, 2022 •
edited
Loading

Note: Currently, we log HTTP 500 errors directly as an exception trace in io.apicurio.registry.services.http.RegistryExceptionMapperService. Add a prefix to the log message, such as Returning an HTTP 5xx because ..., so they can be filtered.

@EricWittmann EricWittmann mentioned this issue Mar 4, 2022
Merged
EricWittmann added a commit that referenced this issue Mar 7, 2022
@EricWittmann
Always log 500 errors, no matter what. Fixes #2232 (#2315)
efe1c9e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@EricWittmann EricWittmann

Labels
component/registry priority/high type/enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Always log 500 errors, no matter what.
2 participants
@jsenko @EricWittmann