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

feat(HttpClient): add span-customization hook

Chiusa
  • Qualcosa non va?
#8,053 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@ArjunCodess ci sta già lavorando.

Dal 19/9/2026.

Valutazione

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

Direzione di ricerca

Start by locating the HttpClient tracing implementation and the existing span-name, whitelisted-header, and redacted-header customization points. Trace where the request, response, and client span are available, then clarify the hook's lifecycle and supported span changes; done means per-request customization covers the stated attributes, status, and kind requirements without replacing the client.

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

Descrizione

enhancement
What is the problem this feature would solve?

The client span that HttpClient creates is almost entirely fixed. Today you can only customize the span name, whitelisted headers, and redacted headers.

So short of replacing the whole client, none of the following is possible per request:

  • Add attributes to just the client span. Effect.annotateSpans reaches it, but it propagates to every span created in scope, so the attribute also lands on nested spans. Effect.annotateCurrentSpan only touches the current span, but the client span is created inside the client call and is never the current span at your call site, so it can't reach it either.
  • Add http.route or another low-cardinality template attribute.
  • Override or redact url.full / url.query / url.path. Query strings and path segments are captured verbatim.
  • Set span status for non-2xx. HttpClient returns 4xx/5xx as a successful response, so the span carries a status_code attribute but no error status.
  • Change the span kind, for example a producer-style fire-and-forget.
What is the feature you are proposing to solve the problem?

A span-customization hook on HttpClient that receives the span along with the request (and the response when available) and can do anything to the span: set or overwrite any attribute (including the built-in url.* ones), add peer.service / http.route / arbitrary attributes, set span status, and set the span kind.

In addition to the hook, maybe we should also provide URL query redaction control, symmetric with CurrentRedactedNames for headers.

What alternatives have you considered?
  • Disable HttpClient's built-in tracing and instrument the calls by hand.
  • Collector-side processors. But it's out of process and the sensitive data leaves your app, so you're relying on the collector to prune it before it's stored or forwarded.
Lingua principale
TypeScript
Stelle
16.7k
Fork
808
Merge medio
10h 49m
PR unite (30g)
846

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 Effect-TS/effect

Tutte le issue di Effect-TS/effect

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.