zipkin-transport-http

import { HttpLogger } from 'zipkin-transport-http'; import { BatchRecorder, Tracer, jsonEncoder } from 'zipkin'; import { SomeContextManager } from 'zipkin-context-cls'; // Or 'zipkin-context-koa', etc. import fetch from 'node-fetch'; // Peer dependency const ZIPKIN_COLLECTOR_URL = process.env.ZIPKIN_COLLECTOR_URL ?? 'http://localhost:9411/api/v2/spans'; const SERVICE_NAME = process.env.SERVICE_NAME ?? 'my-service'; // 1. Create an HTTP Logger const httpLogger = new HttpLogger({ endpoint: ZIPKIN_COLLECTOR_URL, fetch: fetch, jsonEncoder: jsonEncoder.JSON_V2, }); // 2. Create a BatchRecorder with the HTTP Logger const recorder = new BatchRecorder({ logger: httpLogger, }); // 3. Create a Tracer const tracer = new Tracer({ ctxImpl: new SomeContextManager(SERVICE_NAME), // Replace with your chosen context manager recorder: recorder, localServiceName: SERVICE_NAME, }); // Example: Start a new trace and record a span async function doSomeWork() { const rootSpan = tracer.startRootSpan('root-operation'); tracer.scoped(() => { // Perform some work here console.log('Doing some traced work...'); tracer.addBinaryAnnotation('http.url', '/my-endpoint'); tracer.addBinaryAnnotation('http.status_code', '200'); }); rootSpan.finish(); console.log('Trace finished and sent to Zipkin.'); } doSomeWork(); // In a real application, you'd likely want to ensure all spans are flushed on exit. // recorder.flush() can be called manually if needed (e.g., in serverless environments).