Files
d1df5c56ca Improve information architecture for Tempo docs (#5463)
* 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]>
2025-07-31 19:50:31 +05:30

2.7 KiB

title, description, weight, draft
title description weight draft
Choose an instrumentation method Learn about the different instrumentation methods for sending traces to Tempo. 300 true

Choose an instrumentation method

You need to instrument your app to enable it to emit tracing data. This data is then gathered by a collector and sent to Tempo.

Instrumentation methods comparison

You can instrument your code using one or more of the methods described in the table.

Instrumentation method Description Benefits Drawbacks
Automatic instrumentation Applies instrumentation automatically using agents or middleware, without code changes.
  • Quick setup: Enables tracing without code changes
  • Low overhead: Minimal performance impact
  • Limited customization: May not capture all use cases
Zero-code instrumentation Uses eBPF technology to instrument applications without code changes.
  • Non-intrusive: No code changes needed
  • High performance: Low overhead and efficient
  • Limited visibility: May not capture all behavior
  • Complexity: Requires eBPF knowledge
Manual instrumentation Involves adding code to create spans and traces, giving full control over collected data.
  • Full control: Define exactly what data is collected
  • Custom spans: Capture specific behavior
  • Higher effort: Requires code changes and maintenance
  • Potential for errors: Can introduce bugs
Hybrid instrumentation Combines automatic and manual methods, using automatic for most code and manual for custom tracing logic.
  • Flexibility: Leverage benefits of both methods
    • Complexity: May require managing both approaches

      Next steps

      After you choose your instrumentation method, refer to Set up instrumentation.