# Native sidecars (Istio / Envoy) not visible in Application Monitoring mode

**URL:** <https://community.dynatrace.com/t/native-sidecars-istio-envoy-not-visible-in-application-monitoring-mode/55119>\
**Category:** Container platforms\
**Tags:** istio, envoy, kubernetes\
**Created:** [February 26, 2026, 10:25am UTC](https://community.dynatrace.com/t/native-sidecars-istio-envoy-not-visible-in-application-monitoring-mode/55119 "2026-02-26T10:25:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mailvk23](https://avatars.discourse-cdn.com/v4/letter/m/7ba0ec/32.png) [@mailvk23](https://community.dynatrace.com/u/mailvk23)\
**Post date:** [February 26, 2026, 10:25am UTC](https://community.dynatrace.com/t/native-sidecars-istio-envoy-not-visible-in-application-monitoring-mode/55119/1 "2026-02-26T10:25:31Z")

</div>

In Dynatrace Kubernetes **Application Monitoring mode** , native sidecars are not appearing under the **containers list** in the latest Explorer UI.

**Background**

In our setup, Istio runs envoy / istio-proxy as **native sidecars** (initContainers with restartPolicy: Always), which is the newer model promoted by Istio instead of the legacy injected sidecar approach.

However:

- In the **latest Dynatrace Explorer UI** , these istio-proxy containers are not visible.
- This gives the impression that native sidecars are ignored — at least from an **infrastructure/container visibility** perspective (not necessarily deep code monitoring).

**Observations**

- The behavior seems consistent across:
  - Application Monitoring mode
  - CloudNativeFullStack mode ( latest explorer window )

- In **Explorer Classic** , running init containers were previously listed when clicking on containers in a pod, but this is no longer the case in the latest UI.
- Legacy sidecars (regular containers) appear normally.

**Questions**

1. Is this an expected limitation of Dynatrace with Kubernetes native sidecars?
2. Do understand , there could be limitations on DT side to inject on init conatiners, but how kuberenetes platform monitoring is missing it ?
3. Is there any roadmap or workaround to get visibility at least on the infra/container level?

Currently thinking about relying on external metrics sources (Prometheus / node-exporter / Istio metrics) ingested into Dynatrace to track native sidecar resource usage instead.

Would appreciate if anyone has experience dealing with native sidecars or initcontainers+ Dynatrace visibility.

---

<div class="post-metadata">

**Author:** ![kiwibankPL](https://avatars.discourse-cdn.com/v4/letter/k/6f9a4e/32.png) [@kiwibankPL](https://community.dynatrace.com/u/kiwibankPL)\
**Post date:** [October 11, 2026, 11:35pm UTC](https://community.dynatrace.com/t/native-sidecars-istio-envoy-not-visible-in-application-monitoring-mode/55119/2 "2026-10-11T23:35:21Z")

</div>

This is impacting us too! My understanding is that dynatrace doesn’t support native sidecars which has a big impact on our mointorings as dynatrace does not calculate the limits and resourec usage correctly leading to a lot of false positives or missed issues.&nbsp;  
We’ve also found that it impairs autoinstrumentation for some services and they no longer get their services detected by DT

---

<div class="post-metadata">

**Author:** ![kiwibankPL](https://avatars.discourse-cdn.com/v4/letter/k/6f9a4e/32.png) [@kiwibankPL](https://community.dynatrace.com/u/kiwibankPL)\
**Post date:** [October 11, 2026, 11:38pm UTC](https://community.dynatrace.com/t/native-sidecars-istio-envoy-not-visible-in-application-monitoring-mode/55119/3 "2026-10-11T23:38:20Z")

</div>

raised a feature request for this&nbsp;[(1) Support kubernetes native cars - Community Home](https://community.dynatrace.com/post/305204)
