Note: this is a fork of the official repo.
This repository contains set of components extending functionality of the OpenTelemetry SDK. Instrumentation libraries, exporters, and other components can find their home here.
This fork is mainly to fix a critical issue in trace and log correlation when using visualization infrastructure like Grafana Tempo with Grafana Loki.
There are multiple components in this repo and this fork only modifies spdlog-related components. All other components are untouched.
For the spdlog component, this fork automatically injects span id and trace id upon logging. This enables certain infrastructure (e.g., Grafana Tempo and Loki) to correlate logs with the corresponding traces.
See CONTRIBUTING.md
We meet weekly, and the time of the meeting alternates between Monday at 13:00 PT and Wednesday at 9:00 PT. The meeting is subject to change depending on contributors' availability. Check the OpenTelemetry community calendar for specific dates and Zoom meeting links.
Meeting notes are available as a public Google doc. For edit access, get in touch on Slack.
Maintainers (@open-telemetry/cpp-contrib-maintainers):
- Ehsan Saei
- Lalit Kumar Bhasin, Microsoft
- Marc Alff, Oracle
- Tom Tan, Microsoft
Approvers (@open-telemetry/cpp-contrib-approvers):
- DEBAJIT DAS, Cisco
- Johannes Tax, Grafana Labs
- Josh Suereth, Google
- Kumar Pratyush, Cisco
- Max Golovanov, Microsoft
- Siim Kallas, Splunk
- Tobias Stadler
- Tomasz Rojek
- Aryan Ishan, Cisco
Emeritus Maintainer/Approver/Triager:
- None
This repository accepts public contributions. Individual components are developed by numerous contributors. Approvers and maintainers of the main OpenTelemetry C++ SDK repository are not expected to directly contribute to every component.
GitHub CODEOWNERS file is a simple way to automate away some of the pain
associated with the review system on github, by automatically assigning
reviewers to a pull request based on which files were modified. Individual
components are encouraged to propose changes to CODEOWNERS file following
the process described here.
This repository is great for community supported components. Vendor specific code that requires a higher supportability guarantees needs to be placed in vendor's repository. Packages in vendor repositories would be prefixed with the vendor name to signify the difference from community-supported components.