# Deployment was successful, but monitoring data isn't available in Dynatrace **URL:** \ **Category:** Troubleshooting\ **Tags:** kubernetes\ **Created:** [November 30, 2023, 11:22am UTC](https://community.dynatrace.com/t/deployment-was-successful-but-monitoring-data-isnt-available-in-dynatrace/42899 "2023-11-30T11:22:29Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![darynakovyrina](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/darynakovyrina/32/30846_2.png) [@darynakovyrina](https://community.dynatrace.com/u/darynakovyrina)\ **Post date:** [November 30, 2023, 11:22am UTC](https://community.dynatrace.com/t/deployment-was-successful-but-monitoring-data-isnt-available-in-dynatrace/42899/1 "2023-11-30T11:22:29Z")
**DaemonSet** ### Kubernetes ```auto kubectl get pods --namespace=kube-system NAME READY STATUS RESTARTS AGE dynatrace-oneagent-abcde 1/1 Running 0 1m ``` ### OpenShift ```auto oc get pods NAME READY STATUS RESTARTS AGE dynatrace-oneagent-abcde 1/1 Running 0 1m ``` This is typically caused by a timing issue that occurs if application containers have started before OneAgent was fully installed on the system. As a consequence, some parts of your application run uninstrumented. To be on the safe side, OneAgent should be fully integrated before you start your application containers. If your application has already been running, restarting its containers will have the very same effect. ---
**Author:** ![Theodore\_x86](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/theodore_x86/32/17620_2.png) [@Theodore\_x86](https://community.dynatrace.com/u/Theodore_x86)\ **Post date:** [August 1, 2024, 10:32am UTC](https://community.dynatrace.com/t/deployment-was-successful-but-monitoring-data-isnt-available-in-dynatrace/42899/2 "2024-08-01T10:32:58Z")
Hello. This is true but only for the Classic Full-stack Deployment scenario.