# Spurious Skew

**URL:** <https://discuss.elastic.co/t/spurious-skew/220660>\
**Category:** Kibana\
**Created:** [February 24, 2020, 1:14pm UTC](https://discuss.elastic.co/t/spurious-skew/220660 "2020-02-24T13:14:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![hilt86](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hilt86/32/20308_2.png) [@hilt86](https://discuss.elastic.co/u/hilt86)\
**Post date:** [February 24, 2020, 1:14pm UTC](https://discuss.elastic.co/t/spurious-skew/220660/1 "2020-02-24T13:14:59Z")

</div>

I have a visualization of system.network.in.bytes and since 7.6.0 the visualization occasionally gets wrecked by a falsely large value. I have to either refresh or more often than not change the timeframe and it is getting rather annoying 🙂

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/a/5a9754379f2f21fdb14367b72172017e0ad071cd.png)

What is the cause / resolution to this?

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [February 25, 2020, 12:22am UTC](https://discuss.elastic.co/t/spurious-skew/220660/2 "2020-02-25T00:22:21Z")

</div>

Hi, is there anything attributable to the skew, such as a monitored service getting restarted?

---

<div class="post-metadata">

**Author:** ![hilt86](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hilt86/32/20308_2.png) [@hilt86](https://discuss.elastic.co/u/hilt86)\
**Post date:** [February 25, 2020, 12:07pm UTC](https://discuss.elastic.co/t/spurious-skew/220660/3 "2020-02-25T12:07:56Z")

</div>

This is a built-in metric sent by metricbeat, and metricbeat hasn't been restarted nor has my server suddenly sent 338MB/s.

If I set "round to nearest minute / hour" it goes away but I shouldn't need to do this for Kibana to draw an accurate / meaningful graph.

Any idea what is causing this and why the behaviour is different from previous versions?

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [March 3, 2020, 5:12pm UTC](https://discuss.elastic.co/t/spurious-skew/220660/4 "2020-03-03T17:12:03Z")

</div>

Sorry, I can't think of any reason or explanation on the spikes you're seeing. It sounds like the y-axis values could possibly be showing incorrect data based on calculating with partial data buckets, and that might be why the problem goes away when you select "round to the nearest minute / hour"

Would you mind filing a bug in the Kibana source repo with these details? [https://github.com/elastic/kibana/issues/new?template=Bug\_report.md](https://github.com/elastic/kibana/issues/new?template=Bug_report.md)

If you add the `Team:Beats` label to the issue, that will notify the right team.

Thanks very much.

---

<div class="post-metadata">

**Author:** ![hilt86](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hilt86/32/20308_2.png) [@hilt86](https://discuss.elastic.co/u/hilt86)\
**Post date:** [March 5, 2020, 10:19am UTC](https://discuss.elastic.co/t/spurious-skew/220660/5 "2020-03-05T10:19:23Z")

</div>

Could it be because I send metrics every 60s instead of 10s?

---

<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:** [April 2, 2020, 10:19am UTC](https://discuss.elastic.co/t/spurious-skew/220660/6 "2020-04-02T10:19:25Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.