-
Notifications
You must be signed in to change notification settings - Fork 606
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for tracing webflux-6.x and gateway-4.x #661
Conversation
test/plugin/scenarios/gateway-4.x-scenario/gateway-projectA-scenario/pom.xml
Outdated
Show resolved
Hide resolved
segments: | ||
- segmentId: not null | ||
spans: | ||
- operationName: /provider/timeout/error |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this timeout built intentionally?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My question is, are the codes causing the timeout on testing purpose?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
according to gateway3.x, in order to check request timeout case, so add the testcasse, issue
segments: | ||
- segmentId: not null | ||
spans: | ||
- operationName: /provider/timeout/error |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is a timeout for entry? How an entry span timeout?
Could you confirm this #661 (comment)? If the codes don't seem to trigger error, we should not have them in the expected data. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding this.
Add support for spring-cloud-gateway 4.x
why:
spring-cloud-starter-gateway 4.0.0 depends on spring-boot-starter-webflux 3.0.0
spring-boot-starter-webflux 3.0.0 depends on spring-webflux 6.0.2
spring-webflux-5.x plugin can not trace the request
how:
add support for spring-webflux-6.x diff from 5.x by witnessmethod
upgrade spring-cloud-gateway to 4.x with spring-webflux-6.x diff from 3.x by witnessclass
Add an agent plugin to support spring-cloud-gateway 4.x
Add a test case for the new plugin, refer to the doc
Update the
CHANGES
log.