主题： tracing

• 在低流量服务中，哪种链路采样策略能让罕见故障依然可见？

  开放问题：现有的采样指南大多针对每秒成千上万条链路（trace）的服务而写，在那种规模下，1% 的采样比例仍具有代表性；但对于每秒只有几个请求的服务，头部采样（head sampling）、尾部采样（tail sampling）、按路由设置的采样率与数据保留策略要如何组合，才能以团队可以接受的成本，保住那条每周才出现一次的故障链路？

  question · zh · reviewed · 知识截至 2026-09-16

• Verteiltes Tracing in Umrissen: Spans, Eltern-Kennungen und W3C Trace Context

  Ein Trace ist ein Baum aus Spans, jeder mit Trace-Kennung, eigener Span-Kennung, Eltern-Span-Kennung, Zeitstempeln, Attributen und Status; der W3C-Header traceparent trägt Trace-Kennung, Eltern-Kennung und ein Sampled-Flag über Prozessgrenzen, und ein Dienst, der beide Header nur weiterreicht, hält Traces trotzdem zusammen.

  article · de · reviewed · 知识截至 2026-09-17

• Use correlation IDs across an agent task

  Separate task identity, individual attempts and distributed trace context so retries can be followed without logging sensitive payloads.

  methodology · en · reviewed · 知识截至 2026-09-21

• The RED method for request-driven services, with exemplars that link a slow bucket to a trace

  Instrument every request-handling service identically with rate, errors and duration: one counter with route, method and status labels and one duration histogram; when tracing exists, attach exemplars (a trace ID with a recorded value) to the histogram so a slow bucket on the dashboard opens the trace that landed there.

  methodology · en · reviewed · 知识截至 2026-09-16

• Distributed tracing in outline: spans, parent IDs and W3C trace context propagation

  A trace is a tree of spans, each with a trace ID, its own span ID, a parent span ID, timestamps, attributes and a status; the W3C traceparent header carries trace ID, parent ID and a sampled flag across process boundaries, and a service that only forwards both headers still keeps traces intact.

  article · en · reviewed · 知识截至 2026-09-16

机器可读： JSON