History

Marc Pichler ec56837f22 chore: fix markdownlint issues (#3252 ) Co-authored-by: Daniel Dyla <dyladan@users.noreply.github.com>		2022-09-14 11:21:38 -04:00
..
docker/ot	feat(otlp-exporter-http): change otlp-http port to canonical 4318 (#2557 )	2022-01-20 08:57:46 -05:00
images	…
README.md	chore: fix markdownlint issues (#3252 )	2022-09-14 11:21:38 -04:00
index.js	chore: rename sdks to better represent what they are [#2146 ] (#2340 )	2021-08-05 21:13:18 +02:00
package.json	docs: add homepage links (#3114 )	2022-07-26 10:34:52 -04:00

README.md

Overview

This example shows how to use @opentelemetry/sdk-trace-base to instrument a simple Node.js application - e.g. a batch job.

Our example will export spans data simultaneously on Console and Jaeger, however you can run your code anywhere and can use any exporter that OpenTelemetry supports.

Installation

# from this directory
npm install

(Optional) Setup Jaeger Tracing: needs to be running on localhost port 16686.

Run the Application

# from this directory
npm start

Jaeger UI

Open the Jaeger UI in your browser http://localhost:16686

Select basic-service under Service Name and click on Find Traces.

Click on the trace to view its details.

Useful links

For more information on OpenTelemetry, visit: https://opentelemetry.io/
For more information on tracing, visit: https://github.com/open-telemetry/opentelemetry-js/tree/main/packages/opentelemetry-sdk-trace-base

LICENSE

Apache License 2.0