-
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
Metric libbeat.output.write.bytes does not change for type elasticsearch #20752
Comments
Sorry, but I cannot add labels because I am not a contributor. If someone can add tags to the issue, I would be grateful (Filebeat, bug, Team: Integrations). |
Pinging @elastic/integrations-services (Team:Services) |
Any news about this bug? A small addition about the problem. We are using the Filebeat OSS version (We rolled it back to version 7.6.2. The bug was checked on all versions released after 7.6.2.). AWS Elasticsearch version 7.7 acts as the recipient of the logs. |
More users are reporting this issue on discuss: https://discuss.elastic.co/t/filebeat-monitoring-metrics-sent-bytes-and-throughput-shown-as-0/246215 |
Thanks, we'll take a look as soon as possible |
## What does this PR do? This PR passes a missing parameter to the constructor `elasticsearch.Client`. ## Why is it important? The missing parameter prevented Beats from reporting the metrics `libbeat.output.write.bytes` and `libbeat.output.read.bytes` in case of Elasticsearch output. ## Related issues Closes #20752
…1197) ## What does this PR do? This PR passes a missing parameter to the constructor `elasticsearch.Client`. ## Why is it important? The missing parameter prevented Beats from reporting the metrics `libbeat.output.write.bytes` and `libbeat.output.read.bytes` in case of Elasticsearch output. ## Related issues Closes elastic#20752 (cherry picked from commit 78dc0cf)
…1197) ## What does this PR do? This PR passes a missing parameter to the constructor `elasticsearch.Client`. ## Why is it important? The missing parameter prevented Beats from reporting the metrics `libbeat.output.write.bytes` and `libbeat.output.read.bytes` in case of Elasticsearch output. ## Related issues Closes elastic#20752 (cherry picked from commit 78dc0cf)
…21211) * Add Known issues section with an issue about Functionbeat * Fix libbeat.output.*.bytes metrics of Elasticsearch output (#21197) ## What does this PR do? This PR passes a missing parameter to the constructor `elasticsearch.Client`. ## Why is it important? The missing parameter prevented Beats from reporting the metrics `libbeat.output.write.bytes` and `libbeat.output.read.bytes` in case of Elasticsearch output. ## Related issues Closes #20752 (cherry picked from commit 78dc0cf)
…21210) ## What does this PR do? This PR passes a missing parameter to the constructor `elasticsearch.Client`. ## Why is it important? The missing parameter prevented Beats from reporting the metrics `libbeat.output.write.bytes` and `libbeat.output.read.bytes` in case of Elasticsearch output. ## Related issues Closes #20752 (cherry picked from commit 78dc0cf)
Looks like this bug is still present in 7.9.2 version (#21197). |
@kvch can you take a look? |
@EugRomanchenko could you please share the logs of Filebeat? |
Sure.
|
Could you please include lines which include metrics? Lines which start with |
Filebeat Logs
curl -s -XGET 'localhost:5066/stats?pretty'
|
I think the tagging went wrong on the issue. Unfortunately, the fix was not released in v7.9.2. It is going to be published in v7.9.3. I can see it on our 7.9 branch, but it is after the 7.9.2 tag. I am sorry for your inconvenience. |
Thanks. We will wait for the release of 7.9.3. |
…for ES (elastic#21211) * Add Known issues section with an issue about Functionbeat * Fix libbeat.output.*.bytes metrics of Elasticsearch output (elastic#21197) ## What does this PR do? This PR passes a missing parameter to the constructor `elasticsearch.Client`. ## Why is it important? The missing parameter prevented Beats from reporting the metrics `libbeat.output.write.bytes` and `libbeat.output.read.bytes` in case of Elasticsearch output. ## Related issues Closes elastic#20752 (cherry picked from commit ab955b8)
curl -s -XGET 'localhost:5066/stats?pretty'
The text was updated successfully, but these errors were encountered: