القائمة
OpenTelemetry for Cloudflare Workers. Instrument handlers, bindings (KV, R2, D1, AI, Vectorize, Queues, Durable Objects), and global fetch/cache. Multiple API styles for compatibility.
التثبيت باستخدام 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-cloudflare |
| description | OpenTelemetry for Cloudflare Workers. Instrument handlers, bindings (KV, R2, D1, AI, Vectorize, Queues, Durable Objects), and global fetch/cache. Multiple API styles for compatibility. |
Complete OpenTelemetry for Cloudflare Workers. Three API styles, full bindings coverage.
import { instrument, instrumentKV } from 'autotel-cloudflare';
export default instrument(
{
async fetch(req, env, ctx) {
const kv = instrumentKV(env.MY_KV, { name: 'my-kv' });
const val = await kv.get('key'); // traced automatically
return new Response(val);
},
},
{ service: { name: 'my-worker' } },
);
import { wrapModule } from 'autotel-cloudflare';
export default wrapModule(
{ service: { name: 'my-worker' } },
{ async fetch(req, env, ctx) { return new Response('OK'); } },
);
import { trace } from 'autotel-cloudflare';
export default { fetch: trace(async (req) => new Response('OK')) };
Every Cloudflare binding has a wrapper. Each creates spans for all operations.
| Binding | Wrapper | Import |
|---|---|---|
| KV | instrumentKV(env.KV, { name }) | autotel-cloudflare or /bindings |
| R2 | instrumentR2(env.BUCKET, { name }) | same |
| D1 | instrumentD1(env.DB, { name }) | same |
| Service Binding | instrumentServiceBinding(env.SVC, { name }) | same |
| Workers AI | instrumentAI(env.AI) | same |
| Vectorize | instrumentVectorize(env.INDEX, { name }) | same |
| Hyperdrive | instrumentHyperdrive(env.HD, { name }) | same |
| Queue Producer | instrumentQueueProducer(env.QUEUE, { name }) | same |
| Durable Objects | instrumentDO(DOClass) or wrapDurableObject(config, DOClass) | same |
Or use instrumentBindings(env) to auto-instrument all bindings at once.
instrument() and wrapModule() automatically trace: fetch, scheduled, queue, email.
instrumentKV() etc. outside the handler — bindings aren't available at module scope.await import() for dynamic imports — use autotel's safeRequire helpers.autotel-cloudflare/bindings for tree-shaking if you only need binding wrappers.