Skip to content

open-telemetry/opentelemetry-js-contrib

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

9062abf · Jan 17, 2025
Jan 16, 2025
Oct 23, 2024
Jan 17, 2025
Nov 28, 2024
Nov 5, 2024
Jan 17, 2025
Jan 7, 2025
Jan 17, 2025
Jan 10, 2025
Nov 8, 2024
Jun 17, 2019
Jul 12, 2021
Nov 16, 2023
May 30, 2024
Oct 23, 2024
Jun 10, 2019
Nov 16, 2023
Feb 16, 2022
Jan 10, 2025
May 30, 2024
Jan 16, 2025
Jun 20, 2024
Apr 16, 2024
Jun 13, 2024
May 16, 2024
Jul 2, 2019
May 17, 2024
Jun 11, 2024
Jun 11, 2024
Oct 24, 2024
Nov 16, 2023
Nov 5, 2024
Jan 17, 2025
Nov 5, 2024
May 1, 2023
Oct 21, 2024
May 16, 2024
Jun 5, 2023
Jun 5, 2023
Nov 10, 2023
Aug 2, 2023
Oct 7, 2019

Repository files navigation


Getting Started   •   API Documentation

Codecov Status license
test-all-versions badge Beta

Contributing   •   Instrumentations   •   Propagators   •   Examples


OpenTelemetry JavaScript Contrib

A repository for OpenTelemetry JavaScript contributions that are not part of the core repository and core distribution of the API and the SDK.

This project includes:

Instrumentations: OpenTelemetry can collect tracing data automatically using instrumentations. Vendors/Users can also create and use their own. Please read the contributing guidelines on adding new instrumentation before opening any PRs.

Resource Detectors: OpenTelemetry can collect resource attributes of the entity that producing telemetry. For example, a process producing telemetry that is running in a container on Kubernetes has a Pod name, it is in a namespace and possibly is part of a Deployment which also has a name. All three of these attributes can be included in the Resource.

Stability levels

Stability level for components in this repository follow the definitions in CONTRIBUTING.md.

Supported Runtimes

Packages in this repository have a variable range of support for Node.JS and browser versions which for each package depend on

  • the activeness of the owners of those packages,
  • used techniques or runtime features and
  • in the case of the auto-instrumentations, the supported runtime versions for the underlying package.

See the README.md files and the engines field in the package.json files for the respective packages for support information about that package.

See the support section in the core repository for more general information.

Contributing

We'd love your help! Use tags up-for-grabs and good first issue to get started with the project. Follow CONTRIBUTING guide to report issues or submit a proposal.

Thanks to all the people who already contributed

contributors

Useful links

License

Apache 2.0 - See LICENSE for more information.