Showing results for 
Show  only  | Search instead for 
Did you mean: 

Services data not showing in Dynatrace and dashboard, but captured in Dynatrace logs?


We are monitoring Micro Services and observed that even if services are up and running, Dynatrace shows that its processes are off whereas we can see in other tools that it is on. Hence, when we push load on the services, it is not showing on dashboard as well as service detail page. Whats interesting is that, we can see those transactions in Dynatrace logs. Please suggest what might be the case here.



What technology is the service based on? Which log did you look at to verify the transaction on the dynatrace side?

Services are developed in SpringBoot and are deployed on containers (Kubernetes). We looked at Dynatrace logs of hosts on which the service is deployed. We can see the entries in those logs but they are not showing on Dynatrace dashboard or Dynatrace as a whole.

That tech stack is supported and should work automatically. Have you checked the process dashboard of the springboot app, if there where any issues with instrumentation? Are there services discovered for that process?

Yes, there are services discovered for the process. In fact, we could see the data earlier during unit testing. But we do not see data when load testing is was done. If we send 2-3 requests, we can see the data.

Are you sure the load test is going against the same server? It would be quite strange if the same request shows up when executing it manually, but not during the load test.

Did you see any errors in the oneagent logs, especially for the relevant process?

Yes, we verified that the requests are going to the same server. We can see entries in in Dynatrace logs as well. But it does not display in Dynatrace/Dashboard.

We did not see any error in logs for those processes.

I asked team to give some hits to the service. A total of 5 hits were given. I can see those in Dynatrace logs but not on dashboard. No pure-paths are captured. Also, I would like to mention that we could see the data earlier for the same service which means there's no instrumentation issue. We are now facing this with some other services as well.

As @Patrick H. said tell us which technology it is. Also it will be good to check logs from oneagent on hosts that are monitored and affected by this problem. Maybe there is some problem with instrumentation (it technology is supported).