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

FR: metrics and stats

Abierto
#108 0 comentarios 1 reacción 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
docker, prometheus
Área
observability

Línea de trabajo

Use the issue body as the starting specification and separate the operational metrics request from the index metrics request before investigating the project. Identify where component resource usage and repository indexing outcomes are exposed, then verify that Prometheus-format metrics cover the requested file, repository, duration, success, and failure measurements.

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

Descripción

enhancement

This issue is a request for two things that are related but might end up being implemented very differently.
If you want me to break this up into multiple issues, let me know!

The first ask: basic operational metrics.

Currently, I am running this as a docker container and am using Google's ContainerAdvisor to expose basic metrics around CPU/Memory usage. This works well enough since my primary concern is "did I allocate enough RAM to this or should I add more?!". Since there are multiple processes running inside the container, there's no good way to get insight into the memory/cpu...etc of any one component. Not a concern for my purposes, but I can certainly imagine larger deployments where knowing cpu/disk/memory...etc consumption of node vs zoekt would come in very handy.

For these metrics, standard prometheus format would be ideal / most accessible for everybody.

The second ask: metrics about what's in the index.

  • count of files in the index
  • number of repos in the index
  • how long indexing takes (combined with a counter for number of repos, I can calc average index time per repo...)
  • success/fail count per repo (if - suddenly - the number of repos successfully refreshed/indexed inverts with the number of repos that could not be successfully refreshed/indexed, that's an alert that I need to go page somebody to go figure out what's happened to our git server!)
Lenguaje dominante
TypeScript
Estrellas
3.9k
Forks
374
Merge medio
21 h 18 min
PR fusionados (30 d)
39

Guía de contribución

Abrir la guía de contribución

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 sourcebot-dev/sourcebot

Todos los issues de sourcebot-dev/sourcebot

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.