BLOBBER HEALTHCHECK ALERT

A scheduled Git operation checks the health of the blobber's, ensuring the system's blobber are reliable and robust.

BLOBBER'S HEALTHCHECK GITHUB ACTION - https://github.com/0chain/zus-cicd/actions/workflows/network-blobber-check.yaml

INTRODUCTION

Blobbers and their alerts are crucial components of the chain, this git-action checks on their health every three hours.

Keep an eye on the blobber's num_of_block_writes>0 and num_success_challenges, which move every 20 seconds, if you wish to manually verify their health. If any blobber is stuck, this git-action will warn users over devops-0chain Slack Channel.

SCRIPT EXPLANATION

The Script used in GitHub Action - https://github.com/0chain/zus-cicd/blob/main/0chain-scripts/blobber-network-check.sh

Steps followed by above script -

• Fetch sharder links by using https://<< network_name >>/dns/network link.

• Check sharder links are accessible or showing status code other than 200.

• Fetch blobber URLs by using https://<< network_name >>/sharder01/v1/screst/6dba10422e368813802877a85039d3985d96760ed844092319743fb3a76712d7/getblobbers

• Fetch num_of_block_writes and num_success_challenges by using URL https://<< network_name >>/blobber01/_statsJSON

The blobber should withstand tests if it is storing any data:

The following link: https://<< network_name >>/blobber01/_statsJSON , If num_of_block_writes is larger than 0, the JSON that is provided here should have num_success_challenges increasing every 20 seconds.

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.

NOTE - Right now disabled