Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

FR: metrics and stats

Aberta
#108 0 comentários 1 reação 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Stack de tecnologia
docker, prometheus
Domínio
observability

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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!)
Linguagem predominante
TypeScript
Estrelas
3.9k
Forks
374
Merge médio
21h 18min
PRs com merge (30d)
39

Guia de contribuição

Abrir o guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de sourcebot-dev/sourcebot

Todas as issues de sourcebot-dev/sourcebot

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.