<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Deployment was successful, but monitoring data isn't available in Dynatrace in Troubleshooting</title>
    <link>https://community.dynatrace.com/t5/Troubleshooting/Deployment-was-successful-but-monitoring-data-isn-t-available-in/ta-p/230205</link>
    <description>&lt;P&gt;&lt;STRONG&gt;&lt;SPAN class="tag"&gt;DaemonSet&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;DIV&gt;
&lt;H3&gt;Kubernetes&lt;/H3&gt;
&lt;PRE&gt;&lt;CODE&gt;kubectl get pods --namespace=kube-system
NAME                       READY     STATUS              RESTARTS   AGE
dynatrace-oneagent-abcde   1/1       Running             0          1m
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/DIV&gt;
&lt;DIV&gt;
&lt;H3&gt;OpenShift&lt;/H3&gt;
&lt;PRE&gt;&lt;CODE&gt;oc get pods

NAME                       READY     STATUS              RESTARTS   AGE
dynatrace-oneagent-abcde   1/1       Running             0          1m
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/DIV&gt;
&lt;P&gt;This is typically caused by a timing issue that occurs if application containers have started before&amp;nbsp;OneAgent&amp;nbsp;was fully installed on the system. As a consequence, some parts of your application run uninstrumented. To be on the safe side, OneAgent&amp;nbsp;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.&lt;/P&gt;</description>
    <pubDate>Thu, 30 Nov 2023 11:22:29 GMT</pubDate>
    <dc:creator>darynakovyrina</dc:creator>
    <dc:date>2023-11-30T11:22:29Z</dc:date>
    <item>
      <title>Deployment was successful, but monitoring data isn't available in Dynatrace</title>
      <link>https://community.dynatrace.com/t5/Troubleshooting/Deployment-was-successful-but-monitoring-data-isn-t-available-in/ta-p/230205</link>
      <description>&lt;P&gt;&lt;STRONG&gt;&lt;SPAN class="tag"&gt;DaemonSet&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;DIV&gt;
&lt;H3&gt;Kubernetes&lt;/H3&gt;
&lt;PRE&gt;&lt;CODE&gt;kubectl get pods --namespace=kube-system
NAME                       READY     STATUS              RESTARTS   AGE
dynatrace-oneagent-abcde   1/1       Running             0          1m
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/DIV&gt;
&lt;DIV&gt;
&lt;H3&gt;OpenShift&lt;/H3&gt;
&lt;PRE&gt;&lt;CODE&gt;oc get pods

NAME                       READY     STATUS              RESTARTS   AGE
dynatrace-oneagent-abcde   1/1       Running             0          1m
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/DIV&gt;
&lt;P&gt;This is typically caused by a timing issue that occurs if application containers have started before&amp;nbsp;OneAgent&amp;nbsp;was fully installed on the system. As a consequence, some parts of your application run uninstrumented. To be on the safe side, OneAgent&amp;nbsp;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.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Nov 2023 11:22:29 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Troubleshooting/Deployment-was-successful-but-monitoring-data-isn-t-available-in/ta-p/230205</guid>
      <dc:creator>darynakovyrina</dc:creator>
      <dc:date>2023-11-30T11:22:29Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment was successful, but monitoring data isn't available in Dynatrace</title>
      <link>https://community.dynatrace.com/t5/Troubleshooting/Deployment-was-successful-but-monitoring-data-isn-t-available-in/tac-p/252245#M720</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;This is true but only for the Classic Full-stack Deployment scenario.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2024 10:32:58 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Troubleshooting/Deployment-was-successful-but-monitoring-data-isn-t-available-in/tac-p/252245#M720</guid>
      <dc:creator>Theodore_x86</dc:creator>
      <dc:date>2024-08-01T10:32:58Z</dc:date>
    </item>
  </channel>
</rss>

