By submitting, you consent to our use of your data. Privacy Policy.
Category
Business Management
Built by
Beam.ai
Check Kaleido node and network status for failures, then log a ticket with the outage details and flag it urgent once downtime crosses your set threshold.
Node Health Monitoring
Kaleido reports the status of every node in a network, including whether it is syncing, stalled, or fully offline. A Beam agent checks that status on a set interval and, when a node fails and stays down past the account's threshold, opens a ticket with the node ID, network, and time of failure for the infrastructure team. Brief blips that clear on their own within the grace period are logged but not escalated, so the team is not paged for noise. The agent does not restart nodes, change configuration, or add or remove participants, it only reports status within the thresholds the account has set.
Digital Asset Issuance Tracking
Kaleido records each digital asset or token issuance a network processes, including the amount, recipient address, and transaction status. A Beam agent reads new issuance events and checks them against the account's approved limits, such as a maximum issuance amount per request, confirming and logging the ones that fall within range. Any issuance above the limit, tied to an unrecognized address, or reporting a failed transaction gets routed to a person before it is confirmed anywhere else. The agent never initiates an issuance itself, it only confirms and logs activity the network has already processed, within limits the account has set.
Consortium Membership Changes
Kaleido tracks which organizations belong to a consortium network and what permissions each one holds. A Beam agent reads membership and permission records on a schedule and notifies the network admin whenever a participant's status changes, such as a node going inactive or a permission level shifting outside the norm for that member. Changes that match a routine pattern, like a scheduled node rotation already on the calendar, are logged without an alert. Anything unexpected, including a new participant request or an unrecognized permission change, gets routed to a person to approve. The agent does not add, remove, or reconfigure participants on its own.







