mirror of
https://github.com/hanzoai/traces.git
synced 2026-11-03 04:05:45 +00:00
d1df5c56ca
* Migrate changes from Tempo PR Signed-off-by: Jack Baldry <[email protected]> * Updates to resolve conflicts * Move getting started files * Fix aliases * Merge remote-tracking branch 'origin/master' into jdb/2025-07-tempo-set-up-restructure Signed-off-by: Jack Baldry <[email protected]> * Discard changes to content/docs/tempo/next/sync.json * Add aliases Signed-off-by: Jack Baldry <[email protected]> * Fix some aliases Signed-off-by: Jack Baldry <[email protected]> * Updates from rebase * Apply suggestions from code review Co-authored-by: Jack Baldry <[email protected]> * Apply suggestions from code review Co-authored-by: Jack Baldry <[email protected]> * Update content/docs/tempo/next/set-up-for-tracing/instrument-send/set-up-collector/tail-sampling/policies-strategies.md Co-authored-by: Jack Baldry <[email protected]> * Fix links on tile page and test page * Fix links and update missing content * Fix links * Fix links * Fix links and collector text * Updates from Alex's feedback * Link fixes * Fix links in deploy * Fix links * More link fixes * Fix yet more links * Fix more links * Apply suggestions from code review Co-authored-by: Jack Baldry <[email protected]> * Update content/docs/tempo/next/set-up-for-tracing/setup-tempo/test/set-up-test-app.md * Update content/docs/tempo/next/set-up-for-tracing/setup-tempo/test/set-up-test-app.md * Apply suggestions from code review * Add deploy preview workflow Signed-off-by: Jack Baldry <[email protected]> * Updates for Tiffany's suggested edits * Update manifest according to PR instructions --------- Signed-off-by: Jack Baldry <[email protected]> Co-authored-by: Kim Nylander <[email protected]>
1.3 KiB
1.3 KiB
title, menuTitle, description, aliases, weight
| title | menuTitle | description | aliases | weight | ||
|---|---|---|---|---|---|---|
| Instrument for distributed tracing | Instrument for tracing | Client instrumentation is the first building block to a functioning distributed tracing visualization pipeline. |
|
350 |
Instrument for distributed tracing
Client instrumentation is the first building block to a functioning distributed tracing visualization pipeline. Instrumentation handles how traces are generated. To learn more about instrumentation, refer to About instrumentation.
Instrumentation is the act of modifying the source code of a service to emit span information tied to a common trace ID. Traces themselves are a meta-object, comprised of nothing but spans that hold the same ID.
To instrument your application or service, you need to:
- Set up instrumentation to generate traces
- Set up a collector to receive traces from your application