opentelemetry-js/examples/grpc
Daniel Dyla 65b5ba2d04
chore: 0.8.3 release proposal (#1122)
2020-05-28 16:13:08 -04:00
..
images docs(grpc): add grpc example (#326) 2019-09-26 09:35:16 -07:00
README.md Refactor: Consistent package naming and structure (#413) 2019-10-08 22:01:47 +02:00
client.js feat: lint examples (#649) 2020-01-24 08:03:04 -05:00
helloworld_grpc_pb.js feat: lint examples (#649) 2020-01-24 08:03:04 -05:00
helloworld_pb.js feat: lint examples (#649) 2020-01-24 08:03:04 -05:00
package.json chore: 0.8.3 release proposal (#1122) 2020-05-28 16:13:08 -04:00
server.js feat: lint examples (#649) 2020-01-24 08:03:04 -05:00
tracer.js feat: merge user supplied and default plugin configs (#980) 2020-05-26 22:49:42 -07:00

README.md

Overview

OpenTelemetry gRPC 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.

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 zipkin:server
    
  • Run the client

    $ # from this directory
    $ npm run zipkin:client
    

Zipkin UI

zipkin: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 jaeger:server
    
  • Run the client

    $ # from this directory
    $ npm run jaeger:client
    

Jaeger UI

jaeger:server script should output the traceid in the terminal (e.g traceid: 4815c3d576d930189725f1f1d1bdfcc6). Go to Jaeger with your browser http://localhost:50051/trace/(your-trace-id) (e.g http://localhost:50051/trace/4815c3d576d930189725f1f1d1bdfcc6)

LICENSE

Apache License 2.0