So, let's say I have a service-flow where I know (before deployment) is like
Service A-> Service B-> Service C-> Service D.
Good thing about Dynatrace over AppMon is that, it automatically let us know is it handle by the process itself (as I understand it, the 'foreground' thread?) or it is handle by other background thread.
Right now I able to see the truth, which is
Service A-> Service B
Background Thread of Service B -> Service C ->Service D
This is such a good news for the dev and ops, but too bad not so good for management and biz.....because in the service flow I don't see 'end-to-end', but instead two broken flow.
So I am wondering is there any way that we can "link" these two "Broken" service flow together into one?
Answer by Julius L. ·
It's not generally possible without changing the code of the monitored application. Typically those "requests in background threads" are some kind of background processing jobs, doing processing from queue / stack. The other services (web requests / web services / ... ) are pushing data into the queue / stack for further processing. The background execution may happen a long time after the "front-end" request has been processed.
So without changing the code, there is no correlation id and long gaps may happen between those executions.