-
Notifications
You must be signed in to change notification settings - Fork 33
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
Feat performance monitoring #189
Conversation
a3610b4
to
a920d40
Compare
There was a problem hiding this 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
src/query-performance-monitoring/common-utils/common-helpers.go
Outdated
Show resolved
Hide resolved
src/query-performance-monitoring/common-utils/query-fetch-helpers.go
Outdated
Show resolved
Hide resolved
src/query-performance-monitoring/common-utils/query-fetch-helpers.go
Outdated
Show resolved
Hide resolved
src/query-performance-monitoring/performance-metrics/execution_plan_metrics.go
Outdated
Show resolved
Hide resolved
There was a problem hiding this 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
P0 - Unit tests |
There was a problem hiding this 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/query-performance-monitoring/common-utils/common-helpers.go
Outdated
Show resolved
Hide resolved
src/query-performance-monitoring/common-utils/common-helpers.go
Outdated
Show resolved
Hide resolved
src/query-performance-monitoring/common-utils/common-helpers.go
Outdated
Show resolved
Hide resolved
src/query-performance-monitoring/common-utils/ingestion-helpers.go
Outdated
Show resolved
Hide resolved
src/query-performance-monitoring/common-utils/ingestion-helpers.go
Outdated
Show resolved
Hide resolved
src/query-performance-monitoring/common-utils/ingestion-helpers.go
Outdated
Show resolved
Hide resolved
src/query-performance-monitoring/common-utils/ingestion-helpers.go
Outdated
Show resolved
Hide resolved
src/query-performance-monitoring/common-utils/query-fetch-helpers.go
Outdated
Show resolved
Hide resolved
src/query-performance-monitoring/performance-metrics/individual_query_metrics.go
Outdated
Show resolved
Hide resolved
src/query-performance-monitoring/performance-metrics/individual_query_metrics_test.go
Outdated
Show resolved
Hide resolved
src/query-performance-monitoring/performance-metrics/individual_query_metrics.go
Outdated
Show resolved
Hide resolved
46847de
to
8509bcd
Compare
* 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
* resolved : review comments --------- Co-authored-by: Jyothi Surampudi <[email protected]> Co-authored-by: jsurampudi <[email protected]> Co-authored-by: Rahul Reddy <[email protected]>
fix: lint issues --------- Co-authored-by: Jyothi Surampudi <[email protected]> Co-authored-by: jsurampudi <[email protected]> Co-authored-by: Rahul Reddy <[email protected]>
* added more scenerios for unit test cases --------- Co-authored-by: Jyothi Surampudi <[email protected]> Co-authored-by: jsurampudi <[email protected]> Co-authored-by: Rahul Reddy <[email protected]>
* rename variable --------- Co-authored-by: Jyothi Surampudi <[email protected]> Co-authored-by: jsurampudi <[email protected]> Co-authored-by: Rahul Reddy <[email protected]>
resolved : review comments --------- Co-authored-by: Jyothi Surampudi <[email protected]> Co-authored-by: jsurampudi <[email protected]> Co-authored-by: Rahul Reddy <[email protected]>
* remove unused variables --------- Co-authored-by: Jyothi Surampudi <[email protected]> Co-authored-by: jsurampudi <[email protected]> Co-authored-by: Rahul Reddy <[email protected]>
* resolved: review comments --------- Co-authored-by: Jyothi Surampudi <[email protected]> Co-authored-by: jsurampudi <[email protected]> Co-authored-by: Rahul Reddy <[email protected]>
Feat: resolved review comments
* add check while fetching execution plan * resolved : lint issues --------- Co-authored-by: Jyothi Surampudi <[email protected]> Co-authored-by: jsurampudi <[email protected]> Co-authored-by: Rahul Reddy <[email protected]>
Fix: Resolved review comments --------- Co-authored-by: Jyothi Surampudi <[email protected]> Co-authored-by: jsurampudi <[email protected]> Co-authored-by: Rahul Reddy <[email protected]>
fix: lint issues
* execution plan data model fix
* add default description --------- Co-authored-by: Jyothi Surampudi <[email protected]> Co-authored-by: jsurampudi <[email protected]> Co-authored-by: Rahul Reddy <[email protected]>
* feat: resolved review comments * update execution plan schema * feat: change in variable name * feat: change in variable --------- Co-authored-by: Jyothi Surampudi <[email protected]> Co-authored-by: jsurampudi <[email protected]> Co-authored-by: Rahul Reddy <[email protected]>
* feat: resolved review commets * fix: lint issues --------- Co-authored-by: Jyothi Surampudi <[email protected]> Co-authored-by: jsurampudi <[email protected]> Co-authored-by: Rahul Reddy <[email protected]>
c2e75f1
to
58e636e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most of the comments were addressed. Jira's were created to handle Tech Debt. For more info refer
LGTM
daf69cc
into
newrelic:epic_db_query_performance_monitoring
PR to merge performance monitoring code from the fork to the branch
epic_db_query_performance_monitoring