Traces

Capture nested traces during code execution in a vendor agnostic way.

• Zero-overhead if tracing is disabled and minimal overhead if enabled.
• Small opinionated interface with standardised semantics, consistent with the W3C Trace Context Specification.

Please see the project documentation for more details.

• 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.

Please see the project releases for all releases.

• Introduce Traces::Config to Expose prepare Hook

We welcome contributions to this project.

1. Fork it.
2. Create your feature branch (git checkout -b my-new-feature).
3. Commit your changes (git commit -am 'Add some feature').
4. Push to the branch (git push origin my-new-feature).
5. Create new Pull Request.

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.

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.

• 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.