workleap-telemetry-v2

Unify frontend telemetry across Honeycomb, LogRocket, and Mixpanel by calling a single initialization API that configures all platforms together. This solves fragmented instrumentation by managing correlation IDs automatically across tracing, session replay, and product analytics.

Automatic correlation ID propagation is the mechanism of distributing Telemetry Id and Device Id across Honeycomb, LogRocket, and Mixpanel. It links tracing, session replay, and product analytics data together for end-to-end debugging and cross-tool insights without manual tracking.

Initialize telemetry for a frontend application by installing the library, calling initializeTelemetry with platform configurations, and wrapping your app with TelemetryProvider. This sets up unified data flow across initialization and correlation lifecycles.

Yes, you can use optional Noop clients for frontend telemetry testing. They allow you to simulate the initialization and data propagation pipeline without sending actual telemetry data to Honeycomb, LogRocket, or Mixpanel.

Yes, unified telemetry includes privacy safeguards with safe defaults to protect user privacy. Guidance is provided in references to ensure end-to-end debugging and performance monitoring comply with data protection standards during cross-tool analytics.

You need correlation IDs for cross-tool analytics because they link fragmented telemetry data from Honeycomb, LogRocket, and Mixpanel. Matching Telemetry Id and Device Id across platforms enables end-to-end debugging and traces user sessions across tracing and product analytics.