# Metricbeat - network usage data for dashboard

**URL:** <https://discuss.elastic.co/t/metricbeat-network-usage-data-for-dashboard/61906>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [September 30, 2016, 9:22am UTC](https://discuss.elastic.co/t/metricbeat-network-usage-data-for-dashboard/61906 "2016-09-30T09:22:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mha](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mha](https://discuss.elastic.co/u/mha)\
**Post date:** [September 30, 2016, 9:22am UTC](https://discuss.elastic.co/t/metricbeat-network-usage-data-for-dashboard/61906/1 "2016-09-30T09:22:05Z")

</div>

Hi

This one is already closed:

> [@Metricbeat - Can't graph network I/O](https://discuss.elastic.co/t/metricbeat-cant-graph-network-i-o/52387):
>
> Hi there, I'm not sure what to do with the network stats from metricbeat. As it's an incrementing byte counter there's no way I can see to graph this sensibly in Kibana4 - as far as I know there is no derivative graph type (yet). Also with beta3, there are no sample network vis or dashboards supplied, so I don't really know where to start. Is the derivative graph coming to Kibana4, or is there some other way to graph the network stats sent by metricbeat? Thanks

but I still think that it would be really nice feature to have network usage stored also as not incremental values. It would make network dashboard usable (incremental one is useless), and independent from Timelion.

Best

Mikolaj

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [October 3, 2016, 8:30am UTC](https://discuss.elastic.co/t/metricbeat-network-usage-data-for-dashboard/61906/2 "2016-10-03T08:30:20Z")

</div>

Can you share your thoughts on why it is a problem to have it dependent on Timelion? Timelion is directly shipped with Kibana in the 5.0 release.

---

<div class="post-metadata">

**Author:** ![mha](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mha](https://discuss.elastic.co/u/mha)\
**Post date:** [October 4, 2016, 6:23am UTC](https://discuss.elastic.co/t/metricbeat-network-usage-data-for-dashboard/61906/3 "2016-10-04T06:23:47Z")

</div>

1. For scripting purpose it is easier to reuse same template for all metrics.
2. This is the only way to be able to see on a same graph cpu and net usage to track correlation between those metrics.
3. We are trying to implement Watcher. It's impossible to create rules to trigger actions based on incremental data. Using same logic for Watcher and Kibana visualisation makes development much more easy.
4. On a production servers you are not able to always push latest and newest software. Probably we will have kibana 5 not sooner than in a year or so.

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [October 7, 2016, 2:49pm UTC](https://discuss.elastic.co/t/metricbeat-network-usage-data-for-dashboard/61906/4 "2016-10-07T14:49:45Z")

</div>

@mha Thanks for sharing the insights. Could you open a enhancement request issue on Github for further discussions? [https://github.com/elastic/beats](https://github.com/elastic/beats) Point 3 and 4 definitively concern me. For 1 and 2 I hope there are workarounds.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 21, 2016, 9:22am UTC](https://discuss.elastic.co/t/metricbeat-network-usage-data-for-dashboard/61906/5 "2016-10-21T09:22:47Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.