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
Copy file name to clipboardExpand all lines: api/README.md
+1-35Lines changed: 1 addition & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ This package provides everything needed to interact with the OpenTelemetry API,
10
10
11
11
## Quick Start
12
12
13
-
To get started you need to install the SDK and plugins, create a TracerProvider and/or MeterProvider, and register it with the API.
13
+
To get started you need to install the SDK and plugins, create a TracerProvider, and register it with the API.
14
14
15
15
### Install Dependencies
16
16
@@ -23,11 +23,6 @@ $ npm install \
23
23
@opentelemetry/tracing \
24
24
@opentelemetry/exporter-jaeger \ # add exporters as needed
25
25
@opentelemetry/plugin-http # add plugins as needed
26
-
27
-
$ # Install metrics dependencies
28
-
$ npm install \
29
-
@opentelemetry/metrics \
30
-
@opentelemetry/exporter-prometheus # add exporters as needed
31
26
```
32
27
33
28
> Note: this example is for node.js. See [examples/tracer-web](https://github.com/open-telemetry/opentelemetry-js/tree/master/examples/tracer-web) for a browser example.
Because the npm installer and node module resolution algorithm could potentially allow two or more copies of any given package to exist within the same `node_modules` structure, the OpenTelemetry API takes advantage of a variable on the `global` object to store the global API. When an API method in the API package is called, it checks if this `global` API exists and proxies calls to it if and only if it is a compatible API version. This means if a package has a dependency on an OpenTelemetry API version which is not compatible with the API used by the end user, the package will receive a no-op implementation of the API.
@@ -122,7 +96,6 @@ tracerProvider.register({
122
96
If you are writing an instrumentation library, or prefer to call the API methods directly rather than using the `register` method on the Tracer/Meter Provider, OpenTelemetry provides direct access to the underlying API methods through the `@opentelemetry/api` package. API entry points are defined as global singleton objects `trace`, `metrics`, `propagation`, and `context` which contain methods used to initialize SDK implementations and acquire resources from the API.
123
97
124
98
-[Trace API Documentation][trace-api-docs]
125
-
-[Metrics API Documentation][metrics-api-docs]
126
99
-[Propagation API Documentation][propagation-api-docs]
0 commit comments