- https://www.baeldung.com/spring-cloud-sleuth-single-application
- https://coe.gitbook.io/guide/log/sleuth
- https://stackoverflow.com/questions/66517644/java-spring-sleuth-zipkin-x-span-export-not-being-displayed
- https://stackoverflow.com/questions/65846859/how-did-spring-cloud-sleuth-add-tracing-information-to-logback-log-lines/65851232#65851232
- https://cloud.spring.io/spring-cloud-sleuth/2.1.x/multi/multi__features.html
3. Features
RPC tracing is often done automatically by interceptors. Behind the scenes, they add tags and events that relate to their role in an RPC operation. Sometimes, you need to model an asynchronous operation where there is a request but no response. In normal R
cloud.spring.io
Notice the [appname,traceId,spanId,exportable] entries from the MDC:
spanId: The ID of a specific operation that took place.
appname: The name of the application that logged the span.
traceId: The ID of the latency graph that contains the span.
exportable: Whether the log should be exported to Zipkin. When would you like the span not to be exportable? When you want to wrap some operation in a Span and have it written to the logs only.
반응형
'emotional developer > detect-Java' 카테고리의 다른 글
| Spring Boot Architecture (0) | 2023.05.04 |
|---|---|
| Swagger Enum plugin (0) | 2020.10.20 |
| Kafaka consumer listener Sender MDC logging (0) | 2020.10.20 |
