[MAGNOLIA-8503] Ability to log JCR queries Created: 14/Jul/22 Updated: 31/Jan/23 Resolved: 25/Jan/23 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 6.2.21 |
| Fix Version/s: | 6.3.0, 6.2.28 |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
|||||||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||||||||||||||||||||||
| Template: |
|
|||||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
|||||||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
|||||||||||||||||||||||||||||||||||
| Documentation update required: |
Yes
|
|||||||||||||||||||||||||||||||||||
| Date of First Response: | ||||||||||||||||||||||||||||||||||||
| Epic Link: | [JCR] Search Performance issues | |||||||||||||||||||||||||||||||||||
| Sprint: | Nucleus 28 | |||||||||||||||||||||||||||||||||||
| Story Points: | 3 | |||||||||||||||||||||||||||||||||||
| Team: | ||||||||||||||||||||||||||||||||||||
| Work Started: | ||||||||||||||||||||||||||||||||||||
| Description |
|
In Jackrabbit / org.apache.jackrabbit.core.query.QueryImpl, it is possible to turn on debug logs, however this will log every query, not just slow ones. It would be helpful to add logs for slow queries, in similar fashion as for pages which took a long time to render, as this would help identify regular "offenders" and correlate slowness with other events (e.g. concurrent access, CPU activity). |
| Comments |
| Comment by Roman Kovařík [ 12/Jan/23 ] |
|
Discovery:
|