DumbMonit
Monitorare GitLab (self-managed) con DumbMonit
Readiness, Sidekiq backlog, CI runners online or not, pending migrations, instance statistics, sign-up and two-factor settings, licence expiry.
DocumentazioneSito ufficiale: GitLab
Le descrizioni sono in inglese, come nel prodotto. Le etichette della pagina seguono la tua lingua.
Cosa controlla DumbMonit
Whether a self-managed GitLab instance is serving, and whether the parts that quietly carry everything else are keeping up: Sidekiq's queues, the CI/CD runners, database migrations left over from an upgrade, and — for GitLab Enterprise Edition — the licence.
Uso tipico. Forge: Sidekiq backlog, CI runners, pending migrations, sign-up/2FA settings, licence
Esempi
- GitLab Community Edition
- GitLab Enterprise Edition
Come si collega
Cosa serve
- Personal access tokenAn administrator's personal access token, sent as PRIVATE-TOKEN. A token without admin rights still works, but only the version is read.
Porte di rete da aprire
443/TCPAPI (HTTPS, default)80/TCPOnly with the http scheme option
Passaggi di configurazione: Create a read-only token in GitLab
On an administrator account, open avatar → Edit profile → Access → Personal access tokens → Generate token → Legacy token.
Name it as follows, set an expiry date you can renew, and tick only the scope listed below.
dumbmonitGenerate the token and copy it: GitLab shows it only once.
In DumbMonit, enter GitLab's address and paste the token.
To watch CI pipelines, list the numeric project IDs (shown on each project's page) in the Projects watched for CI health option.
Attenzione. GitLab has no read-only administrator role, so the token can read everything its account can: use a dedicated bot account, not your own.