-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[POC] Query-level resource usages instrumentation with SearchPhaseResult #12449
[POC] Query-level resource usages instrumentation with SearchPhaseResult #12449
Conversation
…er on coordinator node
❌ Gradle check result for 05d268d: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Compatibility status:Checks if related components are compatible with change 05d268d Incompatible componentsSkipped componentsCompatible components |
@@ -90,7 +90,7 @@ public static TaskResourceUsage fromXContent(XContentParser parser) { | |||
|
|||
@Override | |||
public String toString() { | |||
return Strings.toString(MediaTypeRegistry.JSON, this, true, true); |
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.
for debugging purpoose only
This PR is stalled because it has been open for 30 days with no activity. |
@ansjcy Are you planning to continue on this PR and targeting any upcoming release? |
This PR is stalled because it has been open for 30 days with no activity. |
Closing this PR - it has been in a draft state since a while. |
SearchPhaseResult
SearchPhaseResult
Bare minimum changes to:
This draft only added instrumentation for query phase and fetch phase.
Description
[Describe what this change achieves]
Related Issues
Resolves #[Issue number to be closed when this PR is merged]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.