# How to estimate Filebeat bandwidth usage based on log size? **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [March 19, 2019, 3:18pm UTC](https://discuss.elastic.co/t/how-to-estimate-filebeat-bandwidth-usage-based-on-log-size/173001 "2019-03-19T15:18:38Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mikesource\_com](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikesource_com/32/42345_2.png) [@mikesource\_com](https://discuss.elastic.co/u/mikesource_com)\ **Post date:** [March 19, 2019, 3:18pm UTC](https://discuss.elastic.co/t/how-to-estimate-filebeat-bandwidth-usage-based-on-log-size/173001/1 "2019-03-19T15:18:38Z")
With the pricing models used in cloud for ingress and egress it has become relevant to understand how much traffic will occur over the course of a year before actually implementing elastic. With this in mind, if I have an application that generates 8 GB of standard application logs (timestamp, type of error and one-liner description of the event). How much bandwidth will Filebeat need to transfer those 8 GB of log text? (considering compression, etc.) ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [March 20, 2019, 10:31pm UTC](https://discuss.elastic.co/t/how-to-estimate-filebeat-bandwidth-usage-based-on-log-size/173001/2 "2019-03-20T22:31:19Z")
You can run Filebeat on your logs and [enable the HTTP endpoint](https://www.elastic.co/guide/en/beats/filebeat/current/http-endpoint.html) in `filebeat.yml` using `http.enabled: true`. This will then let you look at Filebeat's internal metrics by visiting [http://localhost:5066/stats](http://localhost:5066/stats). In the response JSON, if you look under the `libbeat.output.write` key, you'll see how many bytes are being written over the wire by Filebeat. ---
**Author:** ![mikesource\_com](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikesource_com/32/42345_2.png) [@mikesource\_com](https://discuss.elastic.co/u/mikesource_com)\ **Post date:** [March 22, 2019, 7:41pm UTC](https://discuss.elastic.co/t/how-to-estimate-filebeat-bandwidth-usage-based-on-log-size/173001/3 "2019-03-22T19:41:57Z")
This is helpful, but this is when things are running. I meant more as a benchmark or best practice. Here we currently are at a design and MVP phase where we need to be able to estimate the above to determine the feasibility of implementing the stack (to define the non-functional requirement). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 19, 2019, 7:41pm UTC](https://discuss.elastic.co/t/how-to-estimate-filebeat-bandwidth-usage-based-on-log-size/173001/4 "2019-04-19T19:41:59Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.