Eric,
a. Does your license support code level visibility ?
b. if so, check the host and process group displays to see if there is any warning that indicates prevention of instrumentation
Also, from the documentations:
Other reasons services may be classified as opaque
There can be cases where a service is considered opaque even when the service is recognized and of a supported technology. This can occur for the following reasons:
- A process is offline though a service still makes calls to it. These types of opaque services are used to visualize dependencies in the context of availability problems.
- A process never started processing a request (the calling service receives an error or timeout) and therefore Dynatrace cant track the request in the process.
- A process hasn't completely restarted following OneAgent installation. By the time the process restarts, it should no longer appear as opaque.
- The framework processing the request at the specific port is not currently supported by OneAgent. If this is important to you, please submit a Request for Enhancement request for the specific framework and version by visiting our Answers user forum.
- The framework is supported, but OneAgent has run into a technical problem. In such a case, please submit a Support ticket. Describe the issue as best you can and include all details regarding your underlying framework, technologies, and versions.
(https://www.dynatrace.com/support/help/server-side...
Gil.
MaciejNeumann
