DumbMonit
Мониторинг GitLab (self-managed) в DumbMonit
Readiness, Sidekiq backlog, CI runners online or not, pending migrations, instance statistics, sign-up and two-factor settings, licence expiry.
ДокументацияОфициальный сайт: GitLab
Описания на английском, как в самом продукте. Подписи на странице — на вашем языке.
Что проверяет 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.
Типичное применение. Forge: Sidekiq backlog, CI runners, pending migrations, sign-up/2FA settings, licence
Примеры
- GitLab Community Edition
- GitLab Enterprise Edition
Как подключается
Что понадобится
- 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.
Сетевые порты, которые нужно открыть
443/TCPAPI (HTTPS, default)80/TCPOnly with the http scheme option
Шаги настройки: 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.
Обратите внимание. GitLab has no read-only administrator role, so the token can read everything its account can: use a dedicated bot account, not your own.