# Kubernetes and RUM

**URL:** <https://community.dynatrace.com/t/kubernetes-and-rum/39331>\
**Category:** Container platforms\
**Tags:** real-user-monitoring-classic, kubernetes\
**Created:** [April 17, 2023, 3:24pm UTC](https://community.dynatrace.com/t/kubernetes-and-rum/39331 "2023-04-17T15:24:14Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [April 17, 2023, 3:41pm UTC](https://community.dynatrace.com/t/kubernetes-and-rum/39331/2 "2023-04-17T15:41:12Z")

</div>

No, it must be a deep monitored process with OneAgent. If the questions stands for show me the pods in which the traffic from my app ends, then I believe this is doable by querying on entities with the relation filtering.

You should query process group instances (they have the&nbsp;KUBERNETES\_FULL\_POD\_NAME key in the METADATA property) which contain services which are called from the application. Something like this - but keep in mind it must be direct called from the application:

```markup
type(PROCESS_GROUP_INSTANCE),toRelationships.runsOnProcessGroupInstance(type(SERVICE),toRelationships.calls(entityId(APPLICATION-DB5DFB404A9A17C1)))

```

---

_[View the full topic](https://community.dynatrace.com/t/kubernetes-and-rum/39331)._
