7.2. System Health - DevOps

Owned by Denys Tun
Nov 13, 2024
2 min read
image-20241113-132906.png

Admin can review the following information:

Nodes with microservices running inside that node. Admin can use this real time reporting for identifying inconsistencies in node activity and monitor the following parameters in the default node cluster configuration:

  • Node Name - top of box in bold

  • Version of the Service - some services will require individual updates to their node and the corresponding version number is displayed

  • CPU Load - colored bar represents the load

  • Memory Load - colored bar represents the load

  • Uptime in Seconds - easiest way to see when a service restarted

  • Amount of mirco-services running on the node

For deeper review the list of the micro-services running on the node opens by clicking at "Actions" ordered by alphabet.

For deeper review the list of the micro-services running on the node opens by clicking at "Details" and open info Panel with main details about selected node:

System:

  • Uptime in hours,minutes and seconds - easiest way to see when a service restarted

  • Version of the Service

  • CPU Load - colored circle bar represents the load

  • OS memory - colored circle bar represents the load

  • Service memory - colored circle bar represents the load

Requests:

  • Active

  • Total

  • Errored

  • Timeout

Events:

  • Active

  • Total

  • Errored

IMPORTANT!

In case the node goes offline, the according label will appear on top right of the tile.

When the node that has a number in the name goes offline, the replacement node will be deployed by the system automatically and have the same name. but with number -1 or +1.

For example, bitcoin-pi-20 went offline and was replaced by bitcoin-pi-19,

Then bitcoin-pi-19 went offline and was replaced by bitcoin-pi-18.