chore: remove references to NodeTracer

examples/opentracing-shim/shim.js

@@ -1,17 +1,17 @@
 "use strict";
 
-const { NodeTracer } = require("@opentelemetry/node");
+const { NodeTracerRegistry } = require("@opentelemetry/node");
 const { SimpleSpanProcessor } = require("@opentelemetry/tracing");
 const { JaegerExporter } = require("@opentelemetry/exporter-jaeger");
 const { ZipkinExporter } = require("@opentelemetry/exporter-zipkin");
 const { TracerShim } = require("@opentelemetry/shim-opentracing");
 
 function shim(serviceName) {
-  const tracer = new NodeTracer();
+  const registry = new NodeTracerRegistry();
 
-  tracer.addSpanProcessor(new SimpleSpanProcessor(getExporter(serviceName)));
+  registry.addSpanProcessor(new SimpleSpanProcessor(getExporter(serviceName)));
 
-  return new TracerShim(tracer);
+  return new TracerShim(registry.getTracer("opentracing-shim"));
 }
 
 function getExporter(serviceName) {

packages/opentelemetry-node/README.md

@@ -11,14 +11,14 @@ For manual instrumentation see the
 [@opentelemetry/tracing](https://github.com/open-telemetry/opentelemetry-js/tree/master/packages/opentelemetry-tracing) package.
 
 ## How does automated instrumentation work?
-This package exposes a `NodeTracer` that will automatically hook into the module loader of Node.js.
+This package exposes a `NodeTracerRegistry` that will automatically hook into the module loader of Node.js.
 
-For this to work, please make sure that `NodeTracer` is initialized before any other module of your application, (like `http` or `express`) is loaded.
+For this to work, please make sure that `NodeTracerRegistry` is initialized before any other module of your application, (like `http` or `express`) is loaded.
 
 OpenTelemetry comes with a growing number of instrumentation plugins for well know modules (see [supported modules](https://github.com/open-telemetry/opentelemetry-js#plugins)) and an API to create custom plugins (see [the plugin developer guide](https://github.com/open-telemetry/opentelemetry-js/blob/master/doc/plugin-guide.md)).
 
 
-Whenever a module is loaded `NodeTracer` will check if a matching instrumentation plugin has been installed.
+Whenever a module is loaded `NodeTracerRegistry` will check if a matching instrumentation plugin has been installed.
 
 > **Please note:** This module does *not* bundle any plugins. They need to be installed separately.
 
@@ -34,7 +34,7 @@ This instrumentation code will automatically
 In short, this means that this module will use provided plugins to automatically instrument your application to produce spans and provide end-to-end tracing by just adding a few lines of code.
 
 ## Creating custom spans on top of auto-instrumentation
-Additionally to automated instrumentation, `NodeTracer` exposes the same API as [@opentelemetry/tracing](https://github.com/open-telemetry/opentelemetry-js/tree/master/packages/opentelemetry-tracing), allowing creating custom spans if needed.
+Additionally to automated instrumentation, `NodeTracerRegistry` exposes the same API as [@opentelemetry/tracing](https://github.com/open-telemetry/opentelemetry-js/tree/master/packages/opentelemetry-tracing), allowing creating custom spans if needed.
 
 ## Installation
 
@@ -50,14 +50,14 @@ npm install --save @opentelemetry/plugin-https
 
 ## Usage
 
-The following code will configure the `NodeTracer` to instrument `http` using `@opentelemetry/plugin-http`.
+The following code will configure the `NodeTracerRegistry` to instrument `http` using `@opentelemetry/plugin-http`.
 
 ```js
 const opentelemetry = require('@opentelemetry/core');
-const { NodeTracer } = require('@opentelemetry/node');
+const { NodeTracerRegistry } = require('@opentelemetry/node');
 
-// Create and configure NodeTracer
-const tracer = new NodeTracer({
+// Create and configure NodeTracerRegistry
+const registry = new NodeTracerRegistry({
   plugins: {
     http: {
       enabled: true,
@@ -68,25 +68,25 @@ const tracer = new NodeTracer({
   }
 });
 
-// Initialize the tracer
-opentelemetry.initGlobalTracer(tracer);
+// Initialize the registry
+opentelemetry.initGlobalTracerRegistry(registry);
 
 // Your application code - http will automatically be instrumented if
 // @opentelemetry/plugin-http is present
 const http = require('http');
 ```
 
-To enable instrumentation for all [supported modules](https://github.com/open-telemetry/opentelemetry-js#plugins), create an instance of `NodeTracer` without providing any plugin configuration to the constructor.
+To enable instrumentation for all [supported modules](https://github.com/open-telemetry/opentelemetry-js#plugins), create an instance of `NodeTracerRegistry` without providing any plugin configuration to the constructor.
 
 ```js
 const opentelemetry = require('@opentelemetry/core');
-const { NodeTracer } = require('@opentelemetry/node');
+const { NodeTracerRegistry } = require('@opentelemetry/node');
 
-// Create and initialize NodeTracer
-const tracer = new NodeTracer();
+// Create and initialize NodeTracerRegistry
+const registry = new NodeTracerRegistry();
 
-// Initialize the tracer
-opentelemetry.initGlobalTracer(tracer);
+// Initialize the registry
+opentelemetry.initGlobalTracerRegistry(registry);
 
 // Your application code
 // ...

packages/opentelemetry-plugin-dns/README.md

@@ -18,9 +18,9 @@ npm install --save @opentelemetry/plugin-dns
 ## Usage
 
 ```js
-const { NodeTracer } = require('@opentelemetry/node');
+const { NodeTracerRegistry } = require('@opentelemetry/node');
 
-const tracer = new NodeTracer({
+const registry = new NodeTracerRegistry({
   plugins: {
     dns: {
       enabled: true,
@@ -37,7 +37,7 @@ const tracer = new NodeTracer({
 If you use Zipkin, you must use `ignoreHostnames` in order to not trace those calls. If the server is local. You can set :
 
 ```
-const tracer = new NodeTracer({
+const registry = new NodeTracerRegistry({
   plugins: {
     dns: {
       enabled: true,

packages/opentelemetry-plugin-grpc/README.md

@@ -22,9 +22,9 @@ OpenTelemetry gRPC Instrumentation allows the user to automatically collect trac
 
 To load a specific plugin (**gRPC** in this case), specify it in the Node Tracer's configuration.
 ```javascript
-const { NodeTracer } = require('@opentelemetry/node');
+const { NodeTracerRegistry } = require('@opentelemetry/node');
 
-const tracer = new NodeTracer({
+const registry = new NodeTracerRegistry({
   plugins: {
     grpc: {
       enabled: true,
@@ -37,9 +37,9 @@ const tracer = new NodeTracer({
 
 To load all the [supported plugins](https://github.com/open-telemetry/opentelemetry-js#plugins), use below approach. Each plugin is only loaded when the module that it patches is loaded; in other words, there is no computational overhead for listing plugins for unused modules.
 ```javascript
-const { NodeTracer } = require('@opentelemetry/node');
+const { NodeTracerRegistry } = require('@opentelemetry/node');
 
-const tracer = new NodeTracer();
+const registry = new NodeTracerRegistry();
 ```
 
 See [examples/grpc](https://github.com/open-telemetry/opentelemetry-js/tree/master/examples/grpc) for a short example.

packages/opentelemetry-plugin-http/README.md

@@ -22,9 +22,9 @@ OpenTelemetry HTTP Instrumentation allows the user to automatically collect trac
 
 To load a specific plugin (HTTP in this case), specify it in the Node Tracer's configuration.
 ```js
-const { NodeTracer } = require('@opentelemetry/node');
+const { NodeTracerRegistry } = require('@opentelemetry/node');
 
-const tracer = new NodeTracer({
+const registry = new NodeTracerRegistry({
   plugins: {
     http: {
       enabled: true,
@@ -38,9 +38,9 @@ const tracer = new NodeTracer({
 
 To load all the [supported plugins](https://github.com/open-telemetry/opentelemetry-js#plugins), use below approach. Each plugin is only loaded when the module that it patches is loaded; in other words, there is no computational overhead for listing plugins for unused modules.
 ```js
-const { NodeTracer } = require('@opentelemetry/node');
+const { NodeTracerRegistry } = require('@opentelemetry/node');
 
-const tracer = new NodeTracer();
+const registry = new NodeTracerRegistry();
 ```
 
 See [examples/http](https://github.com/open-telemetry/opentelemetry-js/tree/master/examples/http) for a short example.

packages/opentelemetry-plugin-https/README.md

@@ -22,9 +22,9 @@ OpenTelemetry HTTPS Instrumentation allows the user to automatically collect tra
 
 To load a specific plugin (HTTPS in this case), specify it in the Node Tracer's configuration.
 ```js
-const { NodeTracer } = require('@opentelemetry/node');
+const { NodeTracerRegistry } = require('@opentelemetry/node');
 
-const tracer = new NodeTracer({
+const registry = new NodeTracerRegistry({
   plugins: {
     https: {
       enabled: true,
@@ -38,9 +38,9 @@ const tracer = new NodeTracer({
 
 To load all the [supported plugins](https://github.com/open-telemetry/opentelemetry-js#plugins), use below approach. Each plugin is only loaded when the module that it patches is loaded; in other words, there is no computational overhead for listing plugins for unused modules.
 ```js
-const { NodeTracer } = require('@opentelemetry/node');
+const { NodeTracerRegistry } = require('@opentelemetry/node');
 
-const tracer = new NodeTracer();
+const registry = new NodeTracerRegistry();
 ```
 
 See [examples/https](https://github.com/open-telemetry/opentelemetry-js/tree/master/examples/https) for a short example.

packages/opentelemetry-plugin-mongodb-core/README.md

@@ -21,9 +21,9 @@ OpenTelemetry Mongodb Instrumentation allows the user to automatically collect t
 
 To load a specific plugin (mongodb in this case), specify it in the Node Tracer's configuration.
 ```js
-const { NodeTracer } = require('@opentelemetry/node');
+const { NodeTracerRegistry } = require('@opentelemetry/node');
 
-const tracer = new NodeTracer({
+const registry = new NodeTracerRegistry({
   plugins: {
     'mongodb-core': {
       enabled: true,
@@ -36,9 +36,9 @@ const tracer = new NodeTracer({
 
 To load all the [supported plugins](https://github.com/open-telemetry/opentelemetry-js#plugins), use below approach. Each plugin is only loaded when the module that it patches is loaded; in other words, there is no computational overhead for listing plugins for unused modules.
 ```js
-const { NodeTracer } = require('@opentelemetry/node');
+const { NodeTracerRegistry } = require('@opentelemetry/node');
 
-const tracer = new NodeTracer();
+const registry = new NodeTracerRegistry();
 ```
 
 See [examples/mongodb](https://github.com/open-telemetry/opentelemetry-js/tree/master/examples/mongodb-core) for a short example.

packages/opentelemetry-plugin-redis/README.md

@@ -24,9 +24,9 @@ OpenTelemetry Redis Instrumentation allows the user to automatically collect tra
 
 To load a specific plugin (**redis** in this case), specify it in the Node Tracer's configuration
 ```js
-const { NodeTracer } = require('@opentelemetry/node');
+const { NodeTracerRegistry } = require('@opentelemetry/node');
 
-const tracer = new NodeTracer({
+const registry = new NodeTracerRegistry({
   plugins: {
     redis: {
       enabled: true,
@@ -39,9 +39,9 @@ const tracer = new NodeTracer({
 
 To load all the [supported plugins](https://github.com/open-telemetry/opentelemetry-js#plugins), use below approach. Each plugin is only loaded when the module that it patches is loaded; in other words, there is no computational overhead for listing plugins for unused modules.
 ```javascript
-const { NodeTracer } = require('@opentelemetry/node');
+const { NodeTracerRegistry } = require('@opentelemetry/node');
 
-const tracer = new NodeTracer();
+const registry = new NodeTracerRegistry();
 ```
 
 <!-- See [examples/redis](https://github.com/open-telemetry/opentelemetry-js/tree/master/examples/redis) for a short example. -->