DISK ALERT

Disk Alert of servers

INTRODUCTION

Monitoring the health of storage system requires disk alerts. In order to avoid system breakdowns or data loss, GitHub Actions send slack alert on devops-0chain channel to administrators when storage use reaches critical levels. Timely alerts allow for proactive steps like resource reallocation, data cleanup, and storage capacity expansion to ensure smooth system performance and availability, lowering the chance of downtime and preserving maximum operational effectiveness.

This repo schedule disk alert on demo_activeset, zus.network, blog.zus.network, etc

1. It picks disk usage of root disk and send alert in every 6 hours.

2. it send alert on devops-0chain channel.

Git-actions

1. blog.zus.network

2. demo-activeset

3. zus.network

4. test.zus.network

5. test1.zus.network

6. test2.zus.network

7. test3.zus.network

8. testnet.zus.network

Server

1. blog.zus.network is deployed on ec2 instance with wordpress and mysql.

2. demo-activeset is deployed on Hetzner. This includes 4 server.

3. zus.network is main website deployed on ec2 instance.

4. test.zus.network is deployed on hetzner server. This is k8s based deployment on one server.

5. test1.zus.network is deployed on hetzner server. This is k8s based deployment on one server.

6. test2.zus.network is deployed on hetzner server. This is k8s based deployment on one server.

7. test3.zus.network is deployed on hetzner server. This is docker based deployment on 8 servers.

8. testnet1.testnet-0chain.net is deployed on hetzner server.