UPS battery level and power supply check (applicable only to USP power supply scenarios):
Manually check the UPS battery level in case the power supply of the system is interrupted when the server room encounters a power outage.
If the UPS battery level is low, follow the power-off procedure defined by SCP to power off the node in case data corruption occurs.
System configuration backup and verification:
Backup: Back up the system configuration from SCP to the local environment, including the cluster configuration, network configuration, and basic VM configuration.
Verification: Verify the integrity of backup files, such as the file size and format. Make sure that the backup files can be used to restore configuration. For example, you can test backup restoration by simulating the configuration loss scenario.
Platform-wide health check:
Perform a health check, select check items related to system status, configuration, and hardware health. Do not perform the health check during peak hours. For example, perform the health check in the early morning on weekends.
After the health check is complete, search for abnormal check items and provide adjustment plans. For example, adjust the parameters of interfaces if interface configuration anomalies are identified and renew the license key if a license key validity alert is triggered.
Weekly alert review:
Check the total number of alerts within the current week, critical alert fix rate, and regular alert fix rate, and find the reason why alerts are frequently triggered. For example, check whether the CPU usage of nodes frequently exceeds the threshold. If yes, assess whether service migration is required.
Optimize the alert configuration to reduce false positive alerts and false negative alerts. For example, adjust the alert thresholds or add notification recipients.
{{ $t('index.defaultHeader.chromeBrowserTip') }}