Environment health
The Health Check page provides an overview of all your GitGuardian self-hosted instance. On this page, you can have access to the status of the services used by GitGuardian. The page also provides you with information on VCS integration connected to GitGuardian and the Readiness REST endpoint.
GitGuardian Services
This section shows you the status of services used by your GitGuardian instance to function. In case one of those services is somehow unreachable or broken, it will be indicated as such.
Readiness
The REST endpoint checks the readiness of your GitGuardian instance. The URL of that endpoint is displayed on the Health Check page. The endpoint is protected, you can use it only with an API key (refer to the API authentication documentation)
It is easy to use the endpoint, for instance using curl (XXXX
should be
replaced with your API key):
curl -H "Authorization: Token XXXX" https://gitguardian.example.com/exposed/v1/readiness
Example of the reply:
{
"db": "ok",
"redis": "ok",
"status": "ok"
}
Integration Connectivity
Integration health checks (VCS, Messaging, Ticketing, ...) are accessible through Settings > Workspace > Integrations, providing an overview of the source integration status and any errors encountered. In the event of an integration failure, detailed information on resolving the issue will be displayed. Additionally, there's an option to manually re-check the integration connection, along with timestamps indicating the last execution and the most recent successful connection.
You can set up your account to receive email alerts when an integration fails. Find more information here.
Set the interval between periodic health checks by following the instructions below.
KOTS-based Installation
Navigate to Config > Advanced Options in the KOTS Admin Console to access the application settings options.
- Interval between two runs of periodic health checks: Choose from 1min, 3min, 5min, 9min, 15min, 30min, 1h, 2h, 3h, 12h, or 1d (default: 1h).
Helm-based Installation
In your values.yaml
file, add the following configuration, adapted to your needs:
Possible values: 1min, 3min, 5min, 9min, 15min, 30min, 1h, 2h, 3h, 12h, 1d (default: 1h).
settings:
healthCheck:
periodicInterval: "30min"