# Why jitter is missing in the Consumer stats?

**URL:** <https://mediasoup.discourse.group/t/why-jitter-is-missing-in-the-consumer-stats/506>\
**Category:** mediasoup libraries\
**Created:** [January 5, 2020, 4:36am UTC](https://mediasoup.discourse.group/t/why-jitter-is-missing-in-the-consumer-stats/506 "2020-01-05T04:36:43Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\
**Post date:** [January 5, 2020, 4:36am UTC](https://mediasoup.discourse.group/t/why-jitter-is-missing-in-the-consumer-stats/506/1 "2020-01-05T04:36:43Z")

</div>

Why the Consumer statistics does not include `jitter`? The provided [sample stats in the documentation](https://mediasoup.org/documentation/v3/mediasoup/rtc-statistics/#Consumer-Statistics) also confirms that.

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [January 6, 2020, 6:56pm UTC](https://mediasoup.discourse.group/t/why-jitter-is-missing-in-the-consumer-stats/506/2 "2020-01-06T18:56:37Z")

</div>

Because calculating jitter from sender side is not easy at all.

---

<div class="post-metadata">

**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\
**Post date:** [January 7, 2020, 3:12am UTC](https://mediasoup.discourse.group/t/why-jitter-is-missing-in-the-consumer-stats/506/3 "2020-01-07T03:12:23Z")

</div>

Understand, but Jitter is an important WebRTC metric for diagnosing connectivity issues specially for participants (Consumers). Can we hope to have it in the near future? Or do you have any other suggestion/workaround?

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [January 7, 2020, 4:47am UTC](https://mediasoup.discourse.group/t/why-jitter-is-missing-in-the-consumer-stats/506/4 "2020-01-07T04:47:17Z")

</div>

You can get it from local stats in consuming WebRTC devices.

---

<div class="post-metadata">

**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\
**Post date:** [January 7, 2020, 5:56am UTC](https://mediasoup.discourse.group/t/why-jitter-is-missing-in-the-consumer-stats/506/5 "2020-01-07T05:56:10Z")

</div>

Yeah I tried that. Unfortunately the local stats provides `jitter` only for audio. For video I’m getting `jitterBufferDelay` and `jitterBufferEmittedCount` but not `jitter` (tested on Chrome). 😕

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [January 7, 2020, 11:34am UTC](https://mediasoup.discourse.group/t/why-jitter-is-missing-in-the-consumer-stats/506/6 "2020-01-07T11:34:15Z")

</div>

We cannot calculate jitter on a sending RTP stream, just that.

Said that, jitter is not important for video since many RTP packets may belong to the same instant of time and there are retransmissions on another RTX stream. That’s why Chrome does not even show “jitter” for received video streams.

Anyway, we cannot do magic.

---

<div class="post-metadata">

**Author:** ![mkh](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/mkh/32/145_2.png) [@mkh](https://mediasoup.discourse.group/u/mkh)\
**Post date:** [January 7, 2020, 1:03pm UTC](https://mediasoup.discourse.group/t/why-jitter-is-missing-in-the-consumer-stats/506/7 "2020-01-07T13:03:11Z")

</div>

Thanks for the clarification. 👌