Skip to content

Repository to reproduce an issue with manually created traces and disconnected spans within

Notifications You must be signed in to change notification settings

EduardoSimon/otel-async-repro

Repository files navigation

Reproduction Repository for missing context in manual span

The present repository aims to showcase a problem caused when trying to manually instrument a trace split by an async/await block. Please refer to the App component to check the implementation out.

Prerequisites

  • Node (Optional)
  • 🐳 Docker

Usage

For Node users

  1. Install dependencies:
npm install
  1. Run dev server
npm run dev
  1. Open the web server

  2. Click the Test button in the UI

Note: The node version runs the code in development mode Note: The node version outputs the spans to the console.

  1. Check the console to make sure that the parentIds are not properly set

Image

For 🐳 Docker users

  1. Start the cluster
make start
  1. Open the web server

  2. Click the Test button in the UI

  3. Check the trace

Visit Jaeger to debug the trace

You should see the trace disconnected in Jaeger

Note: The docker version runs the code in production, using an nginx to serve the static files and act as a proxy before the otel collector. Doing that, we avoid CORS-related issues. Note: The docker version outputs the spans to Jaeger.

About

Repository to reproduce an issue with manually created traces and disconnected spans within

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published