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

Collect component stdout logs with a filelog receiver

Abierto
  • ¿Algo no está bien?
#1,741 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
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
google-cloud, kubernetes
Área
infrastructure, observability-sre

Línea de trabajo

Start by inspecting the kind manifests and the existing collector Deployment, then trace its logs pipeline configuration. Verify how /var/log/pods, the DaemonSet, k8sattributes, severity parsing, actor labels, and duplicate ateapi events are handled. Done means component logs can be searched across pods and time without losing actor metadata or duplicating lifecycle events.

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

Descripción

area/observability kind/feature

Every ate component writes structured JSON logs to stdout: ateapi, atelet, atecontroller, atenet, ateom, podcertcontroller. Today kubectl logs is the only way to read them, so there's no way to search across components or across time.

Came out of the discussion on #1683.

What we need

  • An optional filelog receiver over /var/log/pods in the kind manifests.
  • That means a DaemonSet collector. The current one is a Deployment with no hostPath.
  • k8sattributes on the logs pipeline, so records get pod and node. Associate on k8s.pod.uid from the path.

Gotchas

  • Set severity parsing explicitly.
  • trace_id, span_id and trace_flags are already top level lowercase hex, so trace_parser maps them with no extra work.
  • ateom wraps actor output with the ate.* keys in a nested group, and the key name differs by environment: labels on kind, logging.googleapis.com/labels on GKE. Handle both or we silently lose every actor on one of them.
  • ateapi also sends its two lifecycle events over OTLP (#1658), so those would arrive twice. Either leave ate-system out of the include globs, or drop records whose scope is github.com/agent-substrate/substrate/internal/actorevent.

cc @JeffLuoo

Lenguaje dominante
Go
Estrellas
4k
Forks
473
Merge medio
2 d 5 h
PR fusionados (30 d)
257

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 agent-substrate/substrate

Todos los issues de agent-substrate/substrate

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.