opentracing-contrib / opentracing-contrib/java-spring-cloud
Could not report to Jaeger when using spring cloud apigw
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 399
- Forks
- 143
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 22
Description
java version: 11
spring cloud version
opentracing-spring-web-starter:4.1.0
spring-cloud-dependencies:Greenwich.SR2
here is sample code snippet:
here is the example:
.route(r -> r
.path("/*/path1", "/*/path2", "/project/*/path2")
.and().method(HttpMethod.GET)
.filters(f -> f.modifyResponseBody(path2WebJson.class, path1WebJson.class,
(exchange, path2WebJson) -> {
path1WebJson path1WebJson = new path1WebJson(path2WebJson.getpath2());
return Mono.just(path1WebJson);
}))
.uri(Url))
.route(r -> r
.path("/*/path1", "/*/path1/*",
"/project/*/path2", "/project/*/path2/*")
.uri(Url))
.build();
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied Spring Cloud route configuration and the listed Java 11, opentracing-spring-web-starter 4.1.0, and Greenwich.SR2 versions; reproduce the missing Jaeger report using the sample routes. Confirm which request path or response-body filter prevents reporting, and consider the issue done when the affected requests produce the expected Jaeger trace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100