Closed AbraDabakra closed 3 days ago
Hi @AbraDabakra I assume you use the default instrumentation?
What technologies are your microservices using for HTTP communication?
Hi @AbraDabakra I assume you use the default instrumentation?
What technologies are your microservices using for HTTP communication?
gRPC,feign, retrofit,restTemplate,Apache HttpClient,OkHttp, webClient
Hi @AbraDabakra, we provide additional instrumentations for the jakarta-Servlet, Apache HttpClient v5 and the Java HttpClient, which are not part of the default instrumentation. You can include them to your microservices. The additional instrumentations are here: https://github.com/inspectIT/inspectit-ocelot-configurations/tree/master/extensions
These should instrument some of your mentioned technologies. I don't believe they will collect data for gRPC, feign, RetroFit and WebClient.
For WebClient, which uses Reactor Netty, we have an incomplete instrumentation in our demo available: https://github.com/inspectIT/inspectit-ocelot-demo/tree/main/configuration-server/files/gateway Maybe it's enough for you.
Other than that, you would need to write new instrumentation by yourself.
I have a config folder, can you tell me how to instrument it correctly? Just add these folders to config???
You already gave me jakarta.json and I just put it in a folder.
Yes, exactly. The agent will also check all subdirectories of your config folder.
@AbraDabakra Did the additional config folders help you in some manner?
@AbraDabakra Closing due to inactivity. Feel free to reopen the issue.
How can I find out why in some microservices I can see http_path (incoming outgoing requests) but in some microservices I can’t see it?
All projects are written in Java 17 Agents used v 2.6.5