17 Jun 2025 07:49 AM
Hi Community,
I am reaching out for assistance regarding an issue, for specific time period, the "Services" data was not visible, although the same data was available in production during that time.
As of now the data appears to be visible again in non-prod . However i would like to understand what caused the data gap and how to identify the root cause of missing traces for that particular period.
What steps or logs should i check to understand what happened during that timeframe and why data was unavailable?
17 Jun 2025 08:00 AM
Hi @yyb55250
https://docs.dynatrace.com/managed/ingest-from/dynatrace-oneagent/oneagent-troubleshooting/oneagent-...
I would check the diagnostic archive within the OneAgent to see if there was a communication outage or possibly an error during monitoring. See the documentation for more details.
17 Jun 2025 08:26 AM
any other alternatives to find out what has happened , why data is unavailable?
17 Jun 2025 08:40 AM
How exactly do missing data in Dynatrace appear?
Could it be a case where the service was simply not called and had no traffic?
Could you please send a screenshot?
17 Jun 2025 10:16 AM
Unfortunately, I am unable to share a screenshot due to access restrictions.
i can see the data now but,
Could you please help me understand why no service data are shown during that period?
17 Jun 2025 10:17 AM
under kubernetes --> selected cluster--> namespace--> workload , when i check a specific workload, the "Services" section shows "No data available" for particular timeframe.
17 Jun 2025 12:24 PM
Unfortunately, based on the information I have from you, it seems that at that time there was no data available for the OneAgent to collect and visualize. You mentioned that the data is missing in the non-production environment, while it is available in the production environment. So it might just be an issue with the timeframe you're looking at in the non-prod environment. Unfortunately, without a support archive, you probably won’t be able to make further progress. I recommend opening a ticket with Dynatrace Support, as they have access to your environment.