Traces
Capture nested traces during code execution in a vendor agnostic way.
Features
- Zero-overhead if tracing is disabled and minimal overhead if enabled.
- Small opinionated interface with standardised semantics, consistent with the W3C Trace Context Specification.
Usage
Please browse the source code index or refer to the guides below.
Getting Started
This guide explains how to use traces for tracing code execution.
Testing
This guide explains how to test traces in your code.
Capture
This guide explains how to use traces for exporting traces from your application. This can be used to document all possible traces.
Releases
Please browse the releases for more details.
v0.14.0
Contributing
We welcome contributions to this project.
- Fork it.
- Create your feature branch (
git checkout -b my-new-feature). - Commit your changes (
git commit -am 'Add some feature'). - Push to the branch (
git push origin my-new-feature). - Create new Pull Request.
Developer Certificate of Origin
In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.
Community Guidelines
This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.
See Also
- traces-backend-open_telemetry — A backend for submitting traces to OpenTelemetry, including ScoutAPM.
- traces-backend-datadog — A backend for submitting traces to Datadog.
- traces-backend-newrelic - A backend for submitting traces to New Relic.
- metrics — A metrics interface which follows a similar pattern.