Golit
search
Error Boundary
Real-time visualization of cluster integrity. Golit isolation protocols ensure that runtime exceptions are confined to the originating node, preventing cascading failures across the DAG topology.
Cluster Health
92.4%
Isolation Status
ACTIVE
account_tree DAG Isolation Map
input
ENTRY_01
warning
storage
settings_ethernet
WORKER_A
database
WORKER_B
Healthy (Isolated)
Failing (Contained)
Protocol: "Golit-Fence-V3" is active. No leak detected.
Error Logs
| Timestamp | Node ID | Exception Type | Severity |
|---|---|---|---|
| 2023-10-27 14:02:11 | NODE_X_FAIL | NullPointerException | Critical |
| 2023-10-27 14:01:55 | NODE_X_FAIL | SocketTimeout | Warning |
| 2023-10-27 14:01:32 | NODE_X_FAIL | MemoryLimitExceeded | Critical |
| 2023-10-27 13:59:44 | NODE_X_FAIL | AccessDeniedException | Critical |
terminal
Stack Trace Inspector
java.lang.NullPointerException: parameter 'payload' cannot be null
at io.golit.core.NodeManager.process(NodeManager.java:142)
at io.golit.runtime.ExecutionEngine.run(ExecutionEngine.java:89)
at io.golit.dag.DAGProcessor.orchestrate(DAGProcessor.java:44) [golit-core-3.1.2.jar]
at java.base/java.lang.Thread.run(Thread.java:833)
// Caused by async event bus delay
at io.golit.events.EventBus.dispatch(EventBus.java:12)
Variables in Context:
node_id: "NODE_X_FAIL"
retries: 3
timeout: 3000ms
isolation: true