Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

MCP: add a structured Cloudflare Workers summary to inspect_span

Aperta
  • Qualcosa non va?
#1,874 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
ai, observability

Direzione di ricerca

Start with the UI Cloudflare adapter in packages/ui/src/lib/cloud-platforms/cloudflare.ts to see how it detects Workers and maps fields, then read apps/ai/src/mcp/tools/inspect-span.ts for the raw attribute output. The change moves detection and mapping into shared pure logic and adds an optional Workers section to the MCP result. Done means tests cover missing fields, zero timing values, and a renamed custom span that keeps its stored name and IDs, and the guidance text covers the clock, sampling, and propagation limits.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

Maple's web UI already interprets Cloudflare Workers attributes, but MCP inspect_span exposes those fields as raw span/resource attribute maps. An agent must repeatedly work out which fields identify the script, version, execution region, CPU time, wall time, TTFB, and Ray ID.

A compact structured Cloudflare summary would make incident analysis more consistent and reduce the amount of attribute interpretation each agent must do.

Existing support and code

Maple already documents native Workers OTLP destinations. Checked against main at 7edfccb17c3f524f9d793e0a11893fcf0535737e:

  • The UI Cloudflare adapter detects Workers and displays script/version, handler, execution model, CPU/wall time, TTFB, colo/region, location, outcome, and Ray ID.
  • inspect_span provides raw attributes and a special decoded view for AI spans.

Proposed change

Add an optional Cloudflare Workers section to the structured and text output of inspect_span. Align its detection and field mapping with the existing UI adapter, preferably through shared pure logic that has no UI dependency.

Include fields when present: script name/version, handler, execution model, colo/region, CPU time in ms, wall time in ms, TTFB in ms, outcome, and Ray ID. Preserve the full raw attribute maps. Missing fields should stay missing; zero is a valid timing value.

Add concise Workers-specific interpretation notes to MCP guidance:

  • Zero-duration spans can result from the Workers clock advancing on I/O; they do not prove that no CPU work occurred.
  • A trace ID in a log or response does not guarantee that spans were stored. Logs can retain IDs when tracing is disabled or a request is not sampled.
  • The current spanContext().traceFlags value does not reflect head sampling and must not be used to construct downstream traceparent headers.
  • Automatic trace-context propagation has limits; missing downstream spans do not prove that no downstream call occurred.

Relation to the latest Cloudflare update

The October 26, 2026 update adds spanContext(), setStatus(), and updateName(). It makes native custom spans easier to identify and interpret. The summary should retain the stored operation name and trace/span IDs so an agent can correlate an application-supplied ID with its renamed operation and Cloudflare context.

The requested Cloudflare summary builds on existing exported attributes. Those attributes predate this update. Generic single-span status exposure is tracked separately in #1873. This Cloudflare summary can be implemented independently.

References: Cloudflare custom-span API and limits, Maple's documented Workers caveats.

Acceptance criteria

  • A native Workers span has a consistent Cloudflare summary in MCP and the web UI.
  • Non-Cloudflare spans retain their current response; empty projected cloudflare.* keys do not cause false detection.
  • Tests cover missing fields, zero timing values, and Cloudflare context supplied through span/resource attributes.
  • A fixture with a renamed custom span retains its stored name and IDs through the MCP result.
  • MCP guidance explains the clock, sampling, and propagation limits without claiming that sampling or a root cause can be determined from those fields alone.

Evidence: source and documentation inspection. A live Cloudflare-to-Maple export has not been tested for this report.

Lingua principale
TypeScript
Stelle
1.8k
Fork
120
Merge medio
8h 11m
PR unite (30g)
667

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di MapleTechLabs/maple

Tutte le issue di MapleTechLabs/maple

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.