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

feat: Enhanced query performance monitoring features to track slow queries, examine query execution plans, monitor wait events, and identify blocking sessions #197

Conversation

abhinav1602
Copy link

@abhinav1602 abhinav1602 commented Jan 8, 2025

feature: Query Performance monitoring for NRI-MSSQL providing Enhanced query performance monitoring features to track the following new event Types:

  • SlowQueryAnalysis
  • WaitTimeAnalysis
  • ExecutionPlanAnalysis
  • BlockedSessionAnalysis

In Progress:

  • Integration tests
  • Unit test cases

abhinav1602 and others added 24 commits January 7, 2025 15:18
handle max values for individual and group query count
Fix get blocking sessions query list order by blocked query start time
remove all linting errors from the code
remove feature and epic branch from workflow
@CLAassistant
Copy link

CLAassistant commented Jan 8, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
3 out of 4 committers have signed the CLA.

✅ abhinav1602
✅ avadla
✅ rahulreddy15
❌ tanushangural
You have signed the CLA already but the status is still pending? Let us recheck it.

@abhinav1602 abhinav1602 changed the title Query analysis ohi feat: Enhanced query performance monitoring features to track slow queries, examine query execution plans, monitor wait events, and identify blocking sessions Jan 8, 2025
@abhinav1602 abhinav1602 closed this Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants