Request to unmonitored hosts

[Swabh]

Hi , Can someone help me understand how is "Request to unmonitored hosts" detected? Is it basis on the code or does oneagent monitor outgoing calls?

I have oneagent running on webservers only. I have not instrumented the appserver. As per my observation the calls from webserver to appserver will not be detected. 

But my client needs a reason why the calls from webserver to appserver not being captured as ' request to unmonitored hosts'.

Thanks in advance!

Swabh

[AntonioSousa · Accepted solution]

@Swabh, In most most cases, I would say they are detected when Dynatrace instruments an application/service, in Full-Stack mode, and then tracks outgoing calls from  those applications. In the case where that request doesn't have a corresponding trace/purepath from the side receiving the request, that is considered a "Request to unmonitored hosts" .

There are lots of associated details. For one, you should consider the differences between "Request to unmonitored hosts" and "Requests to public networks". For this latter one:

• https://docs.dynatrace.com/docs/platform-modules/applications-and-microservices/services/service-mon...

Also, there are "opaque services":

• https://docs.dynatrace.com/docs/platform-modules/applications-and-microservices/services/service-det...

And it's also possible that HTTP headers are being lost, and that typically cuts the association between both traces, creating "Request to unmonitored hosts" on the calling side.

[Theodore_x86]

Hello @AntonioSousa.

What is the difference between unmonitored hosts and Opaque services? To my understaning they both receive requests from monitored hosts but outgoing calls cannot be tracked because instrumentation is missing.

BR

[AntonioSousa]

@Theodore_x86 

On the calling side, when OneAgent sees a call going out from a client to a server, but doesn't receive it on the other side (server side), because there is no OneAGent running on that server, it's a "Request to unmonitored hosts" or "Requests to public networks".

If the same call is made to a server that has OneAgent running, but OneAgent was unable to instrument the process for whatever reasons, an "Opaque service" is created. The links above explain it in quite detail.

[Theodore_x86]

Hello @AntonioSousa

Unmonitored hosts concept is clear.

Opaque services though, I was curious about how Dynatrace understands that a call, which is not received by an instrumented app, is targeted to a Node with OneAgent nevertheless...I guess that targeted hostname after resolved is correlated with "Nodes with Agent installed" names.

BR

[AntonioSousa]

@Theodore_x86 ,

The details of how Dynatrace does it are many times not known. It sees the requests going out on server A, to a server B that Dynatrace knows it has an agent. On server B, it knows which process is listening on each port, has network monitoring, and as such knows it has to be a service of that process. But, once it was unable to instrument that process, an "opaque service" is so created. Once again, this is my interpretation on how it's done 😊