Skip to content

Fulltext queries should be performance traced #5071

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
Closed
tadgh opened this issue Jul 10, 2023 · 0 comments · Fixed by #5072
Closed

Fulltext queries should be performance traced #5071

tadgh opened this issue Jul 10, 2023 · 0 comments · Fixed by #5072

Comments

@tadgh
Copy link
Collaborator

tadgh commented Jul 10, 2023

Currently, only JPA-based performance indicators trigger an invocation of the JPA_PERFTRACE_INFO pointcut. Calls out to the fulltext system are essentially lost from the perspective of the performance tracer.

Suggestion:

  • Fulltext searches or usages of the fulltext index (terminology/search/lastN) should invoke the JPA_PERFTRACE_INFO pointcut.
  • This will help in debugging issues.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add JPA_PERFTRACE_INFO invocation to Fulltext Searches hapifhir/hapi-fhir
1 participant
@tadgh