Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

FR: metrics and stats

Ouverte
#108 0 commentaires 1 réaction 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
docker, prometheus
Domaine
observability

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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!)
Langage dominant
TypeScript
Étoiles
3.9k
Forks
374
Merge moyen
21 h 18 min
PR mergées (30 j)
39

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de sourcebot-dev/sourcebot

Toutes les issues de sourcebot-dev/sourcebot

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.