RANCHER DOWN ALERT

For server instances used in system tests, Kubernetes deployments with the designation "dev-[1:9]" are used. This enables effective testing and validation of Rancher.

Rancher Down Alert GitHub Action Link - https://github.com/0chain/zus-cicd/actions/workflows/rancher-down-alert.yaml

INTRODUCTION

Every three hours, a Git action is planned to check the Rancher link's accessibility, guarantee that it can still be reached, improve system dependability, and give quick insights into any prospective connectivity problems for quick troubleshooting and resolution.

This scheduled Git action sends Slack alerts on devops-0chain channel when a link becomes unavailable, prompting the team to take the necessary corrective action. This minimizes downtime and maintains continuous connectivity for improved system performance and user experience.

Link - rancher.dev-[1:9].devnet-0chain.net

SCRIPT EXPLANATION

The script used in GitHub Action - https://github.com/0chain/zus-cicd/blob/main/0chain-scripts/rancher-down-alert.sh

The script is made to keep track of the rancher link's status code and send out an alert to Slack if it deviates from the expected 200. In line with our goal to provide a smooth user experience, this proactive strategy ensures prompt notifications, enabling quick action to fix possible issues and maintain optimal performance and dependability.

GITHUB ACTION

This GitHub Action is scheduled to run every three hours, but if you want to manually start it, click on Run Workflow and choose the necessary branch from Use workflow from.

Last updated