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 performance monitoring #189

Open
wants to merge 24 commits into
base: epic_db_query_performance_monitoring
Choose a base branch
from

Conversation

rahulreddy15
Copy link
Contributor

@rahulreddy15 rahulreddy15 commented Jan 2, 2025

PR to merge performance monitoring code from the fork to the branch epic_db_query_performance_monitoring

@CLAassistant
Copy link

CLAassistant commented Jan 2, 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 5 committers have signed the CLA.

✅ tharun0064
✅ rahulreddy15
✅ sjyothi54
❌ newrelic-coreint-bot
❌ renovate[bot]
You have signed the CLA already but the status is still pending? Let us recheck it.

@tharun0064 tharun0064 force-pushed the feat_performance_monitoring branch 3 times, most recently from a3610b4 to a920d40 Compare January 8, 2025 06:47
@rahulreddy15 rahulreddy15 changed the base branch from master to epic_db_query_performance_monitoring January 8, 2025 08:35
@rahulreddy15 rahulreddy15 marked this pull request as ready for review January 9, 2025 04:18
@rahulreddy15 rahulreddy15 requested a review from a team as a code owner January 9, 2025 04:18
Copy link
Contributor

@rajrohanyadav rajrohanyadav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, I only reviewed the new code, and would not have 100% confidence on any impacts on the older code. Therefore, additional reviews would be required.

  • As pointed by the linter, some files are not formatted correctly.
  • It is difficult to assert and understand the logic without any comments or unit tests. Can we please add unit tests for all logical functions and utils. Please add any comments helpful to understand what's going on :).
  • I also see some code duplication as pointed by the linter as well. We should check if that can be removed.
  • If we can, I think it can be refactored to only check for version once as the integration is running for a single DBMS, and build our struct based on that, which can still have the same functions for getting query metrics. But use different adapters based on the version. This could remove some duplication and improve readability.
  • It would be helpful if the PR description is updated with some more details and testing details.

Thanks

go.mod Outdated Show resolved Hide resolved
src/args/argument_list.go Outdated Show resolved Hide resolved
src/args/argument_list.go Outdated Show resolved Hide resolved
src/main.go Show resolved Hide resolved
Copy link

@tharun0064 tharun0064 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rajrohanyadav
Thanks for reviewing the PR
can you mention the comments with criticality as P0 ,P1 etc
we will work on them accordingly

@rajrohanyadav
Copy link
Contributor

@rajrohanyadav Thanks for reviewing the PR can you mention the comments with criticality as P0 ,P1 etc we will work on them accordingly

P0 - Unit tests
P1 - Everything else (that we can accomplish) :)

Copy link

@tharun0064 tharun0064 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rajrohanyadav
Added unit test-cases

src/main.go Outdated Show resolved Hide resolved
src/main.go Outdated Show resolved Hide resolved
@rahulreddy15 rahulreddy15 force-pushed the feat_performance_monitoring branch from 46847de to 8509bcd Compare January 16, 2025 13:56
@tharun0064 tharun0064 reopened this Jan 20, 2025
@tharun0064 tharun0064 force-pushed the feat_performance_monitoring branch 2 times, most recently from 3f4d87b to 57bc323 Compare January 21, 2025 12:34
Copy link
Contributor Author

@rahulreddy15 rahulreddy15 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed unit testing for Populate functions.

tharun0064 and others added 21 commits January 23, 2025 17:28
Query performance monitoring

undo change

remove test query

query performance monitoring

undo changelog changes

Query performance monitoring

Query performance monitoring

slow query len check in individual queries metrics populate

trim query text

lint issue fix

undo changelog file change

test

remove OH queries

remove OH queries

reusing existing DB connection (#22)

reusing existing DB connection

DB specific metric collection  (#23)

DB specific metric collection

query response time threshold  (#24)

query response time threshold

change in individual query (#25)

change in individual query

version specific queries  (#26)

verison specific queries

fix database name (#27)

fix database name

test

test

min max threshold on limit (#28)

min max threshold on limit

Feat version specific individual query (#29)

* version specific indivual query

Feat version specific individual query (#30)

Version specific indivual query

fix query id , ingestData:false and reuse individual version specific query (#31)

fix query id , ingestData:false and reuse individual version specific query

database list check (#32)

database list check

publish only if there are metrics (#33)

publish only if there are metrics

undo change log change
Refactor : version specific blocking session annonamization
refactor: resolved review comments

Co-authored-by: jsurampudi <[email protected]>
* refactor: resolved review comments and lint issues

Co-authored-by: tharun0064 <[email protected]>
Refactor : nil checks
* resolved: review comments
* Integration Testing Setup -- Needs Cleanup

* fixed old integration test

* tests now check unsupported containers

* cleanup and fixed linting errors
feat : resolved review comments
 resolved: review comments
* resolved: review comments
Feat: resolved review comments
* Refactored Integration Tests

* Fixed linting errors

* Fixed linting errors again

* Fixed linting errors again again

* Fixed linting errors again again again

* linting is back

* linting is back again

* linting is back again again

* linting is back again again again

* linting is back again again again again
resolved : review comments
fix lint issues
Feat : resolved review comments
* resolved: refactored unit test cases
@rahulreddy15 rahulreddy15 force-pushed the feat_performance_monitoring branch from 090797b to e7dff9d Compare January 23, 2025 11:59
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.

9 participants