Skip to content

I 19 Add support for tracing

Andreas Schlapbach edited this page Oct 28, 2021 · 13 revisions

I-19: Add Support for Distributed Tracing

Description

In order to monitor and troubleshoot microservices-based distributed systems support for tracing is needed.

Owner

  • Schnell Michael (SBB/Lufthansa)
  • Schlapbach Andreas (SBB)

Business Value

In distributed system it is always difficult to determine where any why something fails. This gets even more complicated when multiple providers are involved. Distributed tracing helps pinpoint where failures occur and what causes poor performance. This helps in increasing systems availability and lowering operational cost.

Business Outcomes

*The measurable benefits that the business can anticipate if the epic hypothesis is proven to be correct.3

Supporting the standard helps in increasing systems availability and lowering operational cost.

Leading Indicators

The early measures that will help predict the business outcome hypothesis.

The first implementations of the OSDM specification support open tracing from the start.

Nonfunctional Requirements

Nonfunctional requirements (NFRs) associated with the epic.

Should not increase request or response time.

Context

The tracing implementations are being standardized by WorldWideWeb Consortium (https://www.w3.org/TR/trace-context/). We will adopt this standard which is already supported by major tracing frameworks.

Resolution

Added traceparent and tracestate as headers.

Specification Effort: EXTRA SMALL

Clone this wiki locally