18c6aa4f19
* feat: spike of named tracer registry * chore: mysql/mongo tracer registry support * fix: lint * chore: add getTracer back * chore: change default tracer name to empty string * fix: lint * chore: update examples for registry * chore(tracer-registry): make name required * chore: lint * chore: update examples for required tracer name * chore: remove unused tracer delegate * chore: remove references to basic tracer * chore: remove references to NodeTracer * chore: update xhr for tracer registry * chore: update tracer names to match package names * chore: add version script to all packages * chore: update plugins to use version script * chore: add jsdoc to noop tracer registry * chore: update ioredis for tracer registry * chore: update pg pool for tracer registry * fix: lint * chore: fix tests * chore: lint * chore: lint Co-authored-by: Mayur Kale <mayurkale@google.com> |
||
|---|---|---|
| .. | ||
| images | ||
| README.md | ||
| client.js | ||
| package.json | ||
| server.js | ||
| setup.js | ||
README.md
Overview
OpenTelemetry MySQL Instrumentation allows the user to automatically collect trace data and export them to the backend of choice (we can use Zipkin or Jaeger for this example), to give observability to distributed systems.
This is a modification of the HTTP example that executes multiple parallel requests that interact with a MySQL server backend using the mysql npm module. The example displays traces using multiple connection methods.
- Direct Connection Query
- Pool Connection Query
- Cluster Pool Connection Query
Installation
$ # from this directory
$ npm install
Setup Zipkin Tracing or Setup Jaeger Tracing
Run the Application
Zipkin
-
Run the server
$ # from this directory $ npm run server -
Run the client
$ # from this directory $ npm run client
Zipkin UI
server script should output the traceid in the terminal (e.g traceid: 4815c3d576d930189725f1f1d1bdfcc6).
Go to Zipkin with your browser http://localhost:9411/zipkin/traces/(your-trace-id) (e.g http://localhost:9411/zipkin/traces/4815c3d576d930189725f1f1d1bdfcc6)
Jaeger
-
Run the server
$ # from this directory $ npm run server -
Run the client
$ # from this directory $ npm run client
Jaeger UI
server script should output the traceid in the terminal (e.g traceid: 4815c3d576d930189725f1f1d1bdfcc6).
Go to Jaeger with your browser http://localhost:16686/trace/(your-trace-id) (e.g http://localhost:16686/trace/4815c3d576d930189725f1f1d1bdfcc6)
Useful links
- For more information on OpenTelemetry, visit: https://opentelemetry.io/
- For more information on OpenTelemetry for Node.js, visit: https://github.com/open-telemetry/opentelemetry-js/tree/master/packages/opentelemetry-node
LICENSE
Apache License 2.0