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

Question about v3.0.0 detected Exception #11615

Open
gc-denver opened this issue Oct 25, 2024 · 1 comment
Open

Question about v3.0.0 detected Exception #11615

gc-denver opened this issue Oct 25, 2024 · 1 comment

Comments

@gc-denver
Copy link

gc-denver commented Oct 25, 2024

Hello,
I tested after upgrading from version 2.3.3 to 3.0.0 of Pinpoint.

Although the API logic is successfully executed and the API status code is 200, why is it detected as an Exception in PINPOINT? After running several tests, it seems to occur when there are a large number of insert or update queries. Are there any specific settings I need to adjust?
image

image

Additionally , There were no issues when calling the same API in version 2.3.3.

�Thanks

@kojandy
Copy link
Contributor

kojandy commented Oct 28, 2024

Starting from version 3.0.0, to enhance visibility of potential n+1 queries, if more than 100 queries are executed within a single transaction, it will be marked as an error.

You can disable this feature by adding the option -Dprofiler.sql.error.enable=false, and you can adjust the threshold with the -Dprofiler.sql.error.count option.

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

No branches or pull requests

2 participants