You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current version for each package can be found in the respective `package.json` file for that module. For additional details see the [versioning and stability][spec-versioning] document in the specification.
46
+
The following describes how to set up tracing for a basic web application.
47
+
For more detailed documentation, see the website at <https://opentelemetry.io/docs/instrumentation/js/>.
75
48
76
-
##Quick start
49
+
### Installation
77
50
78
-
### Application Owner
79
-
80
-
#### Install Dependencies
51
+
Dependencies with the `latest` tag on NPM should be compatible with each other.
52
+
See the [version compatibility matrix](#package-version-compatibility) below for more information.
**Note:**`auto-instrumentations-node` is a meta package from [opentelemetry-js-contrib](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/metapackages/auto-instrumentations-node) that provides a simple way to initialize multiple Node.js instrumentations.
The above example will emit auto-instrumented telemetry about your Node.js application to the console. For a more in-depth example, see the [Getting Started Guide](https://opentelemetry.io/docs/js/getting-started/). For more information about automatic instrumentation see [@opentelemetry/sdk-trace-node][otel-node], which provides auto-instrumentation for Node.js applications. If the automatic instrumentation does not suit your needs, or you would like to create manual traces, see [@opentelemetry/sdk-trace-base][otel-tracing]
137
109
138
-
###Library Author
110
+
## Library Author
139
111
140
112
If you are a library author looking to build OpenTelemetry into your library, please see [the documentation][docs]. As a library author, it is important that you only depend on properties and methods published on the public API. If you use any properties or methods from the SDK that are not officially a part of the public API, your library may break if an [Application Owner](#application-owner) uses a different SDK implementation.
141
113
@@ -160,6 +132,30 @@ Please note that versions of Node.JS v8 prior to `v8.12.0` will NOT work, becaus
160
132
Automated browser tests are run in the latest version of Headless Chrome.
161
133
There is currently no list of officially supported browsers, but OpenTelemetry is developed using standard web technologies with wide support and should work in currently supported versions of major browsers.
162
134
135
+
## Package Version Compatibility
136
+
137
+
OpenTelemetry is released as a set of distinct packages in 3 categories: API, stable SDK, and experimental.
138
+
The API is located at [/api](/api/), the stable SDK packages are in the [/packages](/packages/) directory, and the experimental packages are listed in the [/experimental/packages](/experimental/packages/) directory.
139
+
There may also be API packages for experimental signals in the experimental directory.
140
+
All stable packages are released with the same version, and all experimental packages are released with the same version.
141
+
The below table describes which versions of each set of packages are expected to work together.
The current version for each package can be found in the respective `package.json` file for that module. For additional details see the [versioning and stability][spec-versioning] document in the specification.
0 commit comments