Monitoring Managed Service for GitLab instance status
Note
This feature is at the Preview stage.
You can view instance status data in the Monitoring tab on the instance page or in Yandex Monitoring.
Diagnostic information about the instance status is visualized in charts. The charts automatically apply the most appropriate multiple measurement units (GB, percentage, etc.).
You can configure alerts in Yandex Monitoring to receive notifications about cluster failures. In Yandex Monitoring, there are two alert thresholds: Warning and Alarm. If the specified threshold is exceeded, you will receive alerts via the configured notification channels.
Monitoring instance status
To view detailed information about the Managed Service for GitLab instance state:
- Go to Managed Service for GitLab.
- Click the instance name and select the Monitoring tab.
-
To get started with Yandex Monitoring metrics, dashboards, or alerts, click Open in Monitoring in the top panel.
You will see the following charts:
- Data disk: Amount of used and free space on the data storage disk.
- System disk: Amount of used and free space in the system storage.
- CPU: Processor core workload.
- Memory: RAM usage. At high loads, the value of the Available memory parameter goes down and the Used memory values go up.
Setting up alerts in Monitoring
-
In the management console, select the folder with the instance you want to configure alerts for.
-
Go to Monitoring.
-
On the home page, under Service dashboards, select Managed Gitlab.
-
In the chart you need, click and select Create alert.
-
If the selected chart contains multiple metrics in the Alert configuration section, you can keep all data queries or only specific ones. For example, for the System disk metric, you can remove the redundant free storage space query and keep only the used space query.
To remove the redundant query, click → Delete in the query row.
You can learn more about the query language in this Monitoring article.
-
Set the alert trigger conditions:
-
Set the query name that will be used to calculate the alert status.
-
Select the aggregation function to apply to metric values in the time window.
-
Select the comparison function t0 compare the aggregation function result with threshold values.
-
Specify the
WarningandAlarmthreshold values. Select whether the current chart value should be greater than, less than, or equal to the threshold. -
Set the alert calculation time window and delay.
-
-
Click Create.
You can also create alerts for specific Managed Service for GitLab metrics.
Below are the recommended thresholds for some metrics:
The recommended thresholds for the Remaining free disk space (sys.filesystem.FreeB) metric are as follows:
- Aggregation function: Average.
- Comparison function: Less than or equal to.
- Alarm: 7% of the storage size.
- Warning: 10% of the storage size.
- [object Object]: 5 minutes.
- Evaluation delay: 30 seconds.
Instance statuses
The status shows whether the instance is started, stopped, or in intermediate state. You can view the status in the list of Managed Service for GitLab instances or on each instance's page.
The following statuses are possible:
|
Status |
Description |
Suggested actions |
|
CREATING |
Preparing for the first launch |
Wait a while and get started. The time it takes to create an instance depends on the host class. |
|
RUNNING |
The instance is running normally. |
No action is required. |
|
STOPPING |
Stopping the instance |
After a while, the instance status will change to |
|
STOPPED |
The instance is stopped. |
Start the instance to get it running again. |
|
STARTING |
Starting the instance that was stopped earlier |
After a while, the instance status will change to |
|
UPDATING |
Updating the instance |
After the update is completed, the cluster status will switch to |
|
ERROR |
An error occurred that does not allow the instance to continue working |
Run the initial diagnostics:
If you cannot find the cause of the error yourself, contact support. |
|
STATUS_UNKNOWN |
Instance is unable to determine its own status |
Run the initial diagnostics:
If you cannot find the cause of the error yourself, contact support. |
|
DELETING |
Deleting the instance |
Once deleted, the instance will be removed from the Instances list page and will no longer be accessible. No action is required. When you delete an instance, a backup is automatically created and stored for two weeks. If you need to restore the instance after deletion, contact support. |