Codebase list golang-github-go-kit-kit / 32eda3f rfc / rfc006-request-tracing.md
32eda3f

Tree @32eda3f (Download .tar.gz)

rfc006-request-tracing.md @32eda3f — raw · history · blame 

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
---
RFC: 006
Author: Peter Bourgon <peter@bourgon.org>
Status: Draft
---

# Request tracing

## Motivation

[Dapper][]-style request tracing is a necessary introspection tool in any large
distributed system. Gokit services should support request tracing, including
exposition of traces that are compatible with [Zipkin][].

[Dapper]: http://research.google.com/pubs/pub36356.html
[Zipkin]: http://itszero.github.io/blog/2014/03/03/introduction-to-twitters-zipkin

## Scope

- Request tracing SHALL use Dapper terminology: Trace, Span, Tree, etc.

- Regardless if request tracing is enabled or disabled, if incoming requests
  contain trace IDs, package server MUST transparently forward them to
  downstream services.

- If request tracing is enabled, and incoming requests do not contain trace
  IDs, package server SHALL generate relevant IDs and forward them to
  downstream services.

## Implementation

To be defined.