Dynatrace monitoring is Lost after rollout restart of deployment

PavanP — Wed, 24 Jun 2026 03:31:43 GMT

Hi Team,

We are currently facing an issue with Dynatrace monitoring in our containerized application environment.

We are running our workloads on Azure using a containerized setup, where our application is based on Redshift and runs inside Kubernetes pods.

Our application exposes IBM ITX REST APIs, which are actively used and running within these pods.

Dynatrace is configured and actively monitoring these pods using OneAgent.

Whenever we update the configuration and perform a rollout restart of the pods, Dynatrace monitoring initially works as expected.

We are able to see logs and telemetry data appearing correctly in Dynatrace for approximately the first 5 minutes after the restart.

However, after this initial period, Dynatrace stops updating the status, logs, and metrics for the affected pods.

Despite this, the pods continue to run normally without any crashes or restarts, and the application remains fully functional.

Based on our preliminary analysis, it appears that one of the Dynatrace agents is losing monitoring capability for the pods after a few minutes of operation
Please hep on this , thanks

Re: Dynatrace monitoring is Lost after rollout restart of deployment

Julius_Loman — Wed, 24 Jun 2026 06:52:58 GMT

I'd start with looking into OneAgent log files first - typically, look for connectivity issues. That means also logs from the OneAgent processes injected in the application pods. Also, I'd suggest opening a support ticket or an in-product chat to get this resolved faster.

topic Re: Dynatrace monitoring is Lost after rollout restart of deployment in Cloud platforms

Dynatrace monitoring is Lost after rollout restart of deployment

Re: Dynatrace monitoring is Lost after rollout restart of deployment