-
Notifications
You must be signed in to change notification settings - Fork 32
Tracing overview
Lev Khomich edited this page Apr 11, 2014
·
4 revisions
Every message's trace lifecycle consists of several stages:
- Sampling. Before actual trace is created, message needs to be successfully sampled. Such mechanism allows setup tracing extension to sample only some part of messages to reduce overhead when used in production environment.
- Annotating. Any (created) trace can be annotated by basic and binary annotations. Basic annotations contain timestamp and description and can be displayed in timeline. Binary annotations are key-value pairs attached to trace itself.
- Submitting. After some message was explicitly marked as response to traced message, corresponding trace is sent to (external) collector service. If response remains unspecified, trace is sent anyway after some timeout. Any annotations written to already submitted trace are ignored.