Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

`cf workers tail`: no replacement for `wrangler tail`

Abierto
  • ¿Algo no está bien?
#68 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
65/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api, cli

Línea de trabajo

Start with the hand-written registry entry for cf tunnels tail and read usecases/tail-live-worker.yaml and usecases/tail-filtered-worker.yaml to understand the existing gap. Implement the cf workers tail <worker> workflow around tail-session creation and WebSocket consumption; done means unfiltered events stream as JSON by default and replace the basic wrangler tail workflow.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

There is no cf command that streams a Worker's live logs, so a project that
has otherwise moved off Wrangler still has to keep Wrangler installed and
documented for wrangler tail. usecases/tail-live-worker.yaml and
usecases/tail-filtered-worker.yaml already record this as a gap: tail-session
operations are SDK-only, and there is no stream consumer.

Watching a deployed Worker's logs as requests arrive is a basic part of running
one, and it is the last Wrangler-only step in our migration. The dashboard's log
view answers "what happened recently", not "what is happening right now, for the
request I just made".

Expected

A hand-written cf workers tail <worker> that creates a tail session, consumes
the WebSocket, and prints events as JSON by default, matching cf's JSON-first
output. Filters (--status, --method, --search, --ip, --sampling-rate)
would be welcome but are not the blocker; plain unfiltered streaming already
replaces the workflow, since jq can do the rest.

cf tunnels tail is the precedent for a streaming leaf living in the
hand-written registry, so the shape seems to exist already.

Environment

[email protected], @cloudflare/[email protected], [email protected].

Lenguaje dominante
TypeScript
Estrellas
853
Forks
42
Merge medio
17 h 59 min
PR fusionados (30 d)
145

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cloudflare/cf

Todos los issues de cloudflare/cf

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.