菜单
Event subscribers for autotel. PostHog, Mixpanel, Amplitude, Segment, Webhook, Slack. Configure in init() subscribers; use track() or Event from autotel. Import from autotel-subscribers/posthog etc.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill when instrumenting AI/LLM/agent code with OpenTelemetry GenAI semantic conventions — traceGenAI() spans, token usage and cost, gen_ai.* attributes, GenAI metric views, content/evaluation events, the Vercel AI SDK bridge, or the agent identity/delegation/policy/audit governance layer. This is the canonical home for everything GenAI in autotel (the core `autotel` package is AI-free).
Review TypeScript/JavaScript code for OpenTelemetry instrumentation patterns and guide adoption of autotel. Covers Next.js, Nuxt, Nitro, TanStack Start, SvelteKit, NestJS, Express, Hono, Fastify, Elysia, Cloudflare Workers, AWS Lambda, edge runtimes, and standalone Node. Detects unstructured tracing, missing span attributes, manual exporter setup, broken context propagation, exposed PII, and ad-hoc error handling. Covers spans, metrics, logs, structured errors, the autotel processor pipeline (tail-sampling, attribute redaction, span-name normalisation, filtering, baggage), built-in enrichers (user agent, geo, request size) and custom `defineEnricher`, `defineWorkerFetch` for Cloudflare async drains, multi-vendor OTLP backends (Honeycomb, Datadog, Grafana Cloud, Sentry, Axiom, HyperDX), `composeSpanProcessors` / `composeSubscribers` / `composePostProcessors` for pipelines, AI SDK observability with gen-ai semantic conventions, and end-to-end OTLP testing.
Query OpenTelemetry telemetry (traces, metrics, logs, LLM analytics) via the autotel CLI. Use when the user asks about a production issue, slow request, error spike, expensive LLM call, or any "what is happening in my service" question. Each command returns one JSON document on stdout — parse it and answer from the data.
OpenTelemetry instrumentation for MCP (Model Context Protocol). instrumentMCPServer, instrumentMCPClient; W3C trace context via _meta; tools, resources, prompts. Security observability: annotation hints, payload-size & char-budget signals, pluggable prompt-injection classifier, spotlighting.
When to use trace vs span vs request logger vs events in Autotel. Init once at startup, package exports (autotel, autotel/event, autotel/testing). Use for setup and choosing the right API.
trace(), span(), instrument(), init(). Factory vs direct pattern, name inference. Sync init; use node-require for optional deps. Load when wrapping handlers or functions with spans.
| name | autotel-subscribers |
| description | Event subscribers for autotel. PostHog, Mixpanel, Amplitude, Segment, Webhook, Slack. Configure in init() subscribers; use track() or Event from autotel. Import from autotel-subscribers/posthog etc. |
Event subscribers send product/analytics events from autotel to external platforms. Configure subscribers in init(); then use track() or Event from autotel. Each adapter is a separate import path for tree-shaking.
import { init, track } from 'autotel';
import { PostHogSubscriber } from 'autotel-subscribers/posthog';
init({
service: 'my-app',
subscribers: [new PostHogSubscriber({ apiKey: 'phc_...' })],
});
track('order.completed', { userId: 'user-123', amount: 99.99 });
| Platform | Import path | Peer dependency |
|---|---|---|
| PostHog | autotel-subscribers/posthog | posthog-node (optional) |
| Mixpanel | autotel-subscribers/mixpanel | mixpanel (optional) |
| Amplitude | autotel-subscribers/amplitude | @amplitude/analytics-node |
| Segment | autotel-subscribers/segment | @segment/analytics-node |
| Webhook | autotel-subscribers/webhook | none |
| Slack | autotel-subscribers/slack | none |
Install the peer dependency for the subscriber you use (e.g. pnpm add posthog-node for PostHog).
Multiple subscribers: Pass an array to init({ subscribers: [new PostHogSubscriber(...), new MixpanelSubscriber(...)] }). Events are sent to all.
Event instance with overrides: Use Event from autotel/event with a custom subscribers option to send only to specific backends for that instance.
Factories: autotel-subscribers/factories provides createPostHogSubscriber() etc. for env-based config.
Wrong:
import { PostHogSubscriber } from 'autotel-subscribers';
Correct:
import { PostHogSubscriber } from 'autotel-subscribers/posthog';
Each adapter is a separate export; use the subpath so only the adapter you use is bundled.
Source: packages/autotel-subscribers/package.json exports
Subscribers are configured in init(). Without init({ subscribers: [...] }), track() has nowhere to send events. Call init() once at app startup before any track().
Source: packages/autotel/src/event.ts
Install the platform SDK for the subscriber you use (e.g. posthog-node, @segment/analytics-node). Missing peer deps can cause runtime errors or no-op behavior.
Source: packages/autotel-subscribers/package.json peerDependencies
Targets autotel-subscribers v27.x. Requires autotel (workspace). See also: autotel package skill autotel-events for track() and Event API.