[8.3](backport #32197) [Stack Monitoring] Switch cgroup memory fields to keyword#32295
Merged
matschaffer merged 4 commits into8.3from Jul 13, 2022
Merged
[8.3](backport #32197) [Stack Monitoring] Switch cgroup memory fields to keyword#32295matschaffer merged 4 commits into8.3from
matschaffer merged 4 commits into8.3from
Conversation
* [Stack Monitoring] Switch cgroup memory fields to keyword Per https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-nodes-stats.html they should be strings. data.go appears to also consider them strings, so just updating the field definitions might be enough. * make update * Update changelog (cherry picked from commit 1f2895e) # Conflicts: # metricbeat/module/elasticsearch/fields.go
|
This pull request doesn't have a |
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
klacabane
reviewed
Jul 12, 2022
bcc9e7a to
eeeecf3
Compare
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
… fields to keyword (elastic#32295) * [Stack Monitoring] Switch cgroup memory fields to keyword (elastic#32197) * [Stack Monitoring] Switch cgroup memory fields to keyword Per https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-nodes-stats.html they should be strings. data.go appears to also consider them strings, so just updating the field definitions might be enough. * make update * Update changelog (cherry picked from commit 05417e4) # Conflicts: # metricbeat/module/elasticsearch/fields.go * make update * Remove unrelated changelog entries * Put trailing lines back Co-authored-by: Mat Schaffer <mat@elastic.co>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an automatic backport of pull request #32197 done by Mergify.
Cherry-pick of 1f2895e has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com