-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Index cluster_uuid in elasticsearch/node metricset #8771
Index cluster_uuid in elasticsearch/node metricset #8771
Conversation
There still seems to be some troubles with CI |
@ruflin I addressed the CI troubles. Ready for your review again. Thanks! |
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.
Overall LGTM. Should we add a changelog entry as we added a new field?
@@ -48,7 +48,6 @@ func TestFetch(t *testing.T) { | |||
w.WriteHeader(200) | |||
w.Header().Set("Content-Type", "application/json;") | |||
w.Write([]byte(response)) | |||
assert.Equal(t, "/_nodes/_local", r.RequestURI) |
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.
Is this not correct anymore?
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.
It's correct but I removed it because none of the other tests that spin up a HTTP server like this have an assertion in them. Also, for some bizzare reason this test works locally, but only fails in CI.
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.
That it works locally and fails on CI makes me worry now because I think it passed previously.
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.
Alright, digging into it some more...
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.
My bad, I must've been mixing up PRs last night. This test clearly failed locally as well just now (several times) and the issue was obvious. Fixed it in 34310c1.
jenkins, test this |
1 similar comment
jenkins, test this |
None of the other test HTTP servers used in the Metricbeat codebase use an assertion like this so I thought it was safe to get rid of this one.
@ruflin All the things are green now on this PR and review feedback has been addressed. Please take another gander whenever you get a chance. Thanks! [EDIT] As mentioned in another PR comment, I'll add an overall CHANGELOG entry for all these fields in various ES metricsets in the final PR (yet to be put up). |
This PR teaches the
elasticsearch/node
metricset to index the Elasticsearchcluster_uuid
as the module-levelcluster.id
field.