leapwallet / cosmos-node-setup Goto Github PK

AWS EC2 assigns a different IP address when the instance restarts. This causes the monitoring server to generate an alert even though the blockchain node's server is running properly because the monitor is no longer monitoring the correct server. Use elastic IP addresses for the relevant servers to fix this issue.

Check out the Hetzner alternatives Akash, Contable, Linode, Digital Ocean, and Vultr.

Remember to use the builtin Node Exporter integration instead of manually setting it up.

Preferably, make your own dashboard people can use. Otherwise, use the Neobase one that you’re currently using which was shared on the Cerberus Discord server. It must show CPU, RAM, storage, number of API requests made, percentage of API request latencies less than 200 ms, and longest API request latency.

Use the next biggest AWS EC2 instance for monitors because the current instance size is insufficient, and causes the monitor to crash after a while.

Set up Unattended Upgrades.