You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are trying to instrument our microservices using x-ray java agent. Our microservices are implemented using Spring Boot framework. For other microservices, we accomplished the auto instrumentation using the disco plugins by adding environment variables to our applications as below.
Also we are using ZuulFilter to add custom headers to incoming requests' header. Could this also be an issue for our error that we encounter, how can we move forward from here? 🙏
The text was updated successfully, but these errors were encountered:
yukselcodingwithyou
changed the title
Using X-Ray Agent in Spring Boot API Gateway
Using X-Ray Agent in Spring Boot & Zuul Proxy API Gateway
Dec 1, 2021
Apologies for the delayed response. Just to confirm, when you mention your Zuul proxy API Gateway, you're referring to a service that you own and not AWS's API Gateway service right?
Regardless, I'm not too sure about this issue as I haven't seen it before but perhaps it is related to FasterXML/jackson-modules-base#131 based on a quick google search. Currently the agent pulls in v2.11.0, so it could be that upgrading the agent's version would fix this. Is there any way you could provide some reproduction code for this, so we can verify the fix?
Also, just as an FYI, if you're still having the X-Ray java agent feel free to try out the AWS Distro for OpenTelemetry Java Agent. It natively supports instrumenting many more libraries/frameworks, and has 1st-class support for X-Ray.
We are trying to instrument our microservices using x-ray java agent. Our microservices are implemented using Spring Boot framework. For other microservices, we accomplished the auto instrumentation using the disco plugins by adding environment variables to our applications as below.
But in our API Gateway, we failed to do so. While we try to trace any request from our API Gateway, we came across an error like this below:
Also in our x-ray daemon running locally, we encountered with this warning below:
To resolve this error, we tried to exclude plugin path from command like below:
But there was no segment sent to the daemon that is running locally. Then we tried to add the plugins to its path one by one,
First, we added the two jars above to disco-plugins path above, there was no error, but segment also not sent to our daemon .
Then, we added the jar below and, we saw that this error is related to this plugin, with some dependencies that we use in our API Gateway application.
Also we are using
ZuulFilter
to add custom headers to incoming requests' header. Could this also be an issue for our error that we encounter, how can we move forward from here? 🙏The text was updated successfully, but these errors were encountered: