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.

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

RESTEasy Reactive: log exceptions #27585

Closed
FroMage opened this issue Aug 30, 2022 · 2 comments · Fixed by #27595
Closed

RESTEasy Reactive: log exceptions #27585

FroMage opened this issue Aug 30, 2022 · 2 comments · Fixed by #27595
Labels
Milestone

Comments

@FroMage
Copy link
Member

FroMage commented Aug 30, 2022

Description

On #27526 I noticed that we have no option to log exceptions on the server, before we map them to an exception handler, which sometimes just turns them into a blank HTTP error. In the case of native executable debugging, this can be helpful.

We could log them under the ERROR level, or add a config option to log them.

Implementation ideas

No response

@quarkus-bot
Copy link

quarkus-bot bot commented Aug 30, 2022

/cc @geoand, @stuartwdouglas

@geoand
Copy link
Contributor

geoand commented Aug 30, 2022

We probably want to log them as debug by default in order to not cause excessive logging (which can be a security issue).

geoand added a commit to geoand/quarkus that referenced this issue Aug 30, 2022
geoand added a commit that referenced this issue Aug 30, 2022
Add high level logging for RESTEasy Reactive exceptions
@quarkus-bot quarkus-bot bot added this to the 2.13 - main milestone Aug 30, 2022
fercomunello pushed a commit to fercomunello/quarkus that referenced this issue Aug 31, 2022
@gsmet gsmet modified the milestones: 2.13 - main, 2.12.1.Final Sep 5, 2022
gsmet pushed a commit to gsmet/quarkus that referenced this issue Sep 5, 2022
evanchooly pushed a commit to nenros/quarkus that referenced this issue Sep 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants