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

correct format for memory module in dockerbeat #4619

Merged
merged 2 commits into from
Jul 11, 2017

Conversation

stickperson
Copy link
Contributor

As discussed here, docker.memory.usage.pct in dockerbeat was off by a factor of 100. As per @andrewkroh, I updated the fields.

@elasticmachine
Copy link
Collaborator

Can one of the admins verify this patch?

@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically on build-eu-00. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@exekias
Copy link
Contributor

exekias commented Jul 6, 2017

thanks @stickperson! You need to run make update after changing fields.yml, so documentation and internal files get updated. Build is failing because of that, give it a try and push new changes :)

@andrewkroh
Copy link
Member

Thanks for fixing the issue. Could you please add a line to the CHANGELOG.asciidoc under the bugfix section for Metricbeat.

@andrewkroh
Copy link
Member

jenkins, test it

@andrewkroh andrewkroh merged commit 539df96 into elastic:master Jul 11, 2017
@stickperson stickperson deleted the fix-memory-format branch July 11, 2017 04:40
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.

4 participants