workleap/wl-telemetry · Archived

workleap-telemetry-v2

Guide for Workleap's telemetry solution (@workleap/telemetry) that unifies Honeycomb, LogRocket, and Mixpanel with consistent correlation IDs. Use this skill when: (1) Initializing wl-telemetry in a frontend application (2) Working with correlation values (Telemetry Id, Device Id) and their lifecycle (3) Using Honeycomb for distributed tracing and performance analysis (4) Creating and enriching Honeycomb traces/spans using OpenTelemetry (5) Using LogRocket for session replay and frontend debugg…

First seen Feb 12, 2026

Installation

$ npx skills add workleap/wl-telemetry --skill workleap-telemetry-v2

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from workleap/wl-telemetry.

npx skills add workleap/wl-telemetry

Browse all from workleap/wl-telemetry

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSE
Default branch main
Open issues 14
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,851 B
  • docs SUMMARY.md 974 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Workleap Telemetry (wl-telemetry)

@workleap/telemetry is an umbrella package that integrates Honeycomb, LogRocket, and Mixpanel with consistent correlation IDs for unified debugging and analysis.

Core Concepts

Correlation Values

Two automatic correlation IDs unify all telemetry platforms:

ID Purpose Honeycomb LogRocket/Mixpanel
Telemetry Id Single app load app.telemetry_id Telemetry Id
Device Id Device across sessions app.device_id Device Id

If LogRocket is enabled, Honeycomb and Mixpanel automatically receive app.logrocketsessionurl / LogRocket Session URL.

Platform Roles

  • Honeycomb: Distributed traces, performance monitoring, RUM metrics (LCP, CLS, INP)
  • LogRocket: Session replay, frontend debugging, user experience investigation
  • Mixpanel: Product analytics, event tracking, user behavior insights

Quick Start

import { initializeTelemetry, TelemetryProvider } from "@workleap/telemetry/react";

const telemetryClient = initializeTelemetry({
  logRocket: { appId: "your-app-id" },
  honeycomb: {
    namespace: "your-namespace",
    serviceName: "your-service",
    apiServiceUrls: [/.+/g],
    options: { proxy: "https://your-otel-proxy" }
  },
  mixpanel: {
    productId: "wlp",
    envOrTrackingApiBaseUrl: "production"
  }
});

// Wrap application
<TelemetryProvider client={telemetryClient}>
  <App />
</TelemetryProvider>

Using Platform Clients

// Access via hooks
const telemetryClient = useTelemetryClient();
const honeycombClient = useHoneycombInstrumentationClient();
const logRocketClient = useLogRocketInstrumentationClient();
const mixpanelClient = useMixpanelClient();
const track = useMixpanelTrackingFunction();

Storybook/Testing (Noop Clients)

import { NoopTelemetryClient, TelemetryProvider } from "@workleap/telemetry/react";

const telemetryClient = new NoopTelemetryClient();

<TelemetryProvider client={telemetryClient}>
  <Story />
</TelemetryProvider>

Detailed References

  • Full API Reference: See [references/api.md](references/api.md) for complete APIs
  • Integration Patterns: See [references/integrations.md](references/integrations.md) for platform-specific patterns
  • Usage Examples: See [references/examples.md](references/examples.md) for common patterns

Critical Rules

  1. Use umbrella package - Always use @workleap/telemetry, not standalone packages
  2. Do not invent APIs - Only use documented APIs from references
  3. Correlation is automatic - Never manually set Telemetry Id or Device Id
  4. Noop for non-production - Use NoopTelemetryClient in Storybook/tests
  5. Privacy matters - Never log PII to LogRocket; use data-public/data-private attributes