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

A separate metric for actual network-transmitted bytes? #10184

Open
shapirus opened this issue Apr 8, 2025 · 0 comments
Open

A separate metric for actual network-transmitted bytes? #10184

shapirus opened this issue Apr 8, 2025 · 0 comments

Comments

@shapirus
Copy link

shapirus commented Apr 8, 2025

Is your feature request related to a problem? Please describe.

There is currently no way of telling how much data fluentbit transmits over the network to the log ingester without analyzing the ingester's http access logs or looking at the ingester's own metrics (if it has them at all).

Yes we have the fluentbit_output_proc_bytes_total, but it apparently counts the bytes before they are fed into the http client for transmission, and when the data is compressed before transmission (using gzip in my case), the actual amount transferred over the network becomes lower than that reported in fluentbit_output_proc_bytes_total.

Describe the solution you'd like

It would be nice to add a new metric to fluentbit such as fluentbit_output_http_sent_bytes_total that would measure actual bytes sent.

Additional context

Use case: traffic accounting for cost estimation and optimization in cloud-hosted environments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant