# Bug for key-request count on dashboard

**URL:** <https://community.dynatrace.com/t/bug-for-key-request-count-on-dashboard/19705>\
**Category:** Dashboarding\
**Tags:** real-user-monitoring-classic, dashboards-classic\
**Created:** [June 29, 2020, 8:25pm UTC](https://community.dynatrace.com/t/bug-for-key-request-count-on-dashboard/19705 "2020-06-29T20:25:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MAkimov](https://avatars.discourse-cdn.com/v4/letter/m/b77776/32.png) [@MAkimov](https://community.dynatrace.com/u/MAkimov)\
**Post date:** [June 29, 2020, 8:25pm UTC](https://community.dynatrace.com/t/bug-for-key-request-count-on-dashboard/19705/1 "2020-06-29T20:25:15Z")

</div>

I added a metric count of key requests to dashboard.

 ![25507-screenshot-27.png](https://global.discourse-cdn.com/dynatrace/original/3X/f/9/f9d99630f7fad2e6455d790cdc9d1050a4613ee5.png)

we see on the dashboard an amount equal to **16**

metric → **Request Count** of Key-request

 ![25489-screenshot-30.png](https://global.discourse-cdn.com/dynatrace/original/3X/f/9/f90e0c7664047c6c7d1b0fe4335668df4c926369.png)

but when I go drill-down into key-request diagnostics, I see a different amount

 ![25526-screenshot-28.png](https://global.discourse-cdn.com/dynatrace/original/3X/9/7/97eae1a354ea14b7462054f97f538f1b63a0dc37.png)

**it is only**  **4 purepath**

 ![25527-screenshot-29.png](https://global.discourse-cdn.com/dynatrace/original/2X/0/019062933854e55fdd35e47d850bc01f7c180f6b.png)

**Is it bug ?**

---

<div class="post-metadata">

**Author:** ![matt\_gibiec](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/matt_gibiec/32/8626_2.png) [@matt\_gibiec](https://community.dynatrace.com/u/matt_gibiec)\
**Post date:** [June 30, 2020, 1:06am UTC](https://community.dynatrace.com/t/bug-for-key-request-count-on-dashboard/19705/2 "2020-06-30T01:06:24Z")

</div>

Hey Mikhali,

The number of PPs will almost always be less than the number of actual requests as Dynatrace samples the data on the PP level and groups PPs together if they are very similar to each other in their performance. If you hover over one of the PPs you will be able to see phrases like “5 other PPs like this one”.

I hope this helps!

Thanks,

MG

---

<div class="post-metadata">

**Author:** ![MAkimov](https://avatars.discourse-cdn.com/v4/letter/m/b77776/32.png) [@MAkimov](https://community.dynatrace.com/u/MAkimov)\
**Post date:** [June 30, 2020, 8:02am UTC](https://community.dynatrace.com/t/bug-for-key-request-count-on-dashboard/19705/3 "2020-06-30T08:02:36Z")

</div>

Hello , Thank you for answer.

Could you please send a link to the documentation where it is described.

I was told that dynatrace captures every operation without aggregation and sampling.

And if I capture different request attributes (for example, transaction id), then it turns out I can’t see them?

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [June 30, 2020, 12:51pm UTC](https://community.dynatrace.com/t/bug-for-key-request-count-on-dashboard/19705/4 "2020-06-30T12:51:19Z")

</div>

This happens typically for Adaptive Traffic Management. If your process group instance is called more often than the limit (1000 request/minute), some requests are not captured and you get “x other purepaths like this”.

See more details here:  
[https://www.dynatrace.com/support/help/how-to-use-dynatrace/transactions-and-services/monitoring/adaptive-traffic-management-and-control/](https://www.dynatrace.com/support/help/how-to-use-dynatrace/transactions-and-services/monitoring/adaptive-traffic-management-and-control/)

In Managed, you can increase the limit, but it may result into increased overhead. In SaaS you cannot get captured more than 1000 PP/minute from a process group instance.
