spring.sleuth.remote-fields
vs spring.sleuth.baggage.remote-fields
baggage.
whereas in the documentation withoutZipkinAutoConfiguration.REPORTER_BEAN_NAME
with my own XRayUDPReporter
bean? There doesn't seem to be any auto-config for the Zipkin X-Ray but I'm happy to be wrong.
Hi I now have traces being sent to X-Ray but the names that display in the X-Ray console for traces are not being correctly set for Feign and Spring Cloud Stream Kafka. For Feign they are using the http method, here is an example the name
is get
but the annotations.http_path
has the path:
"subsegments": [
{
"id": "f945f28acb910a16",
"name": "get",
"start_time": 1591611761.254306,
"end_time": 1591611761.583249,
"http": {
"request": {
"method": "GET"
}
},
"annotations": {
"http_path": "/device/v1",
"operation": "get"
},
"namespace": "remote"
},
...
For Spring Cloud Stream Kafka I was hoping it would resolve the destination of the channel but at the moment it is using the binder as the name
and the channel is in the annotations. It doesnt seem to have resolved the destination.
{
"id": "aeab33b8a6b2c004",
"name": "kafka",
"start_time": 1591611763.963422,
"end_time": 1591611763.968351,
"annotations": {
"channel": "output"
},
"namespace": "remote"
}
Do you know if its possible to override the name
? So far I've tried @SpanName
and @PostMapping(name = "my-name"
but neither work.
Hello,
I m trying to propagate some extra-information within all log records (in my current service and client services) using spring-cloud-sleuth 2.2.1.RELEASE, but facing a problem when trying to add local-keys to SLF4J's MDC. (it works perfectly with propagation-keys for remote calls). This is my configuration:
spring:
sleuth:
propagation-keys:
- remote-key
local-keys:
- local-key
propagation:
tag:
whitelisted-keys:
- remote-key
- local-key
log:
slf4j:
whitelisted-mdc-keys:
- remote-key
- local-key
I'm i missing some thing? or log.slf4j.whitelisted-mdc-keys is not intended to work with local-keys?
Thank you in advance.