Tracing and instrumentation based on OpenTracing.
These projects are well documented, and should be sufficient to help you get started with tracing RecallGraph (or any other trace-enabled foxx microservice). To get started, you can begin with the foxx-tracer documentation. Some of those instructions are repeated here for quick reference.
- 2.In RecallGraph's settings, there is a param named
sampling-probability. You can set this to a value between 0 and 1 (both inclusive) to tell the tracer how often to record a trace for incoming requests. For example, if
sampling-probability = 0.1, then roughly 1 out of 10 requests will be traced. Regardless of this param's value, a trace can be force-recorded or force-suppressed using the
x-force-sampleheader parameter. See Recording Traces for details.
For all HTTP endpoints, there are 4 trace-specific headers available that can be used for the following:
- 1.Propagate a running trace from the client to your application.
- 2.Force the application to record or suppress a trace for the request, regardless of the
The headers (all optional) are as follows: