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

Output IO counters #1806

Merged
merged 2 commits into from
Jun 7, 2016
Merged

Output IO counters #1806

merged 2 commits into from
Jun 7, 2016

Conversation

urso
Copy link

@urso urso commented Jun 6, 2016

introduce counters (bytes send/received and errors) to elasticsearch, logstash
and redis outputs

@ruflin
Copy link
Contributor

ruflin commented Jun 7, 2016

LGTM. Some of the tests fail.

@zstyblik
Copy link
Contributor

zstyblik commented Jun 7, 2016

Hello,

is documentation for this feature planned as well? Or, please, can you provide me with link to documentation related to this feature?

Thank you.

@urso urso force-pushed the enh/io-stats branch 2 times, most recently from 780c364 to 6dd78e8 Compare June 7, 2016 15:19
introduce counters (bytes send/received and errors) to elasticsearch, logstash
and redis outputs
@urso
Copy link
Author

urso commented Jun 7, 2016

@zstyblik this is currently for internal use only. We're considering some proper monitoring support for beats, but this is not it.

@ruflin ruflin merged commit c054bef into elastic:master Jun 7, 2016
@urso urso deleted the enh/io-stats branch June 8, 2016 12:16
@jstangroome
Copy link

Even just in this form, this kind of IO monitoring would be extremely useful.

For the "proper monitoring support" you are considering, is there a thread somewhere we can follow?

@ruflin
Copy link
Contributor

ruflin commented Jun 13, 2016

Best is to follow this issue here: #463

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