Diagnose production issues in running Ergo Framework distributed systems via MCP.
npx skills add https://github.com/3commas-io/commas-claude --skill ergo-devops
Please help me install this Agent Skill. Skill: ergo-devops Source: https://github.com/3commas-io/commas-claude/tree/main/skills/ergo-devops Command: npx skills add https://github.com/3commas-io/commas-claude --skill ergo-devops
This Skill helps diagnose and resolve production issues in running Ergo Framework nodes by providing tools to inspect performance, identify bottlenecks, and understand system behavior.
Use the ergo-devops skill to find processes with high mailbox latency on the 'ergo-node-1' node.
High-intent search queries and answers about installing and using this skill.
To diagnose production issues in a running Ergo Framework distributed system, you need to inspect process states, collect CPU and memory profiles, and analyze network connections to identify root causes like bottlenecks or leaks. This approach pinpoints performance bottlenecks, memory issues, and restart loops via MCP.
The best way to find the cause of an unresponsive Ergo node is to collect CPU profiles, inspect goroutine states, and analyze network connections to pinpoint the exact system behavior causing the failure. This identifies memory leaks, network problems, and stuck processes.
To profile CPU and memory usage on a live Ergo node, utilize built-in profiling and process state inspection tools to identify performance bottlenecks and memory issues. This helps understand system behavior and resolve restart loops.
Yes, you can inspect goroutine states to detect process leaks and stuck processes in Ergo. This allows you to monitor system behavior and resolve performance bottlenecks in running distributed nodes via MCP. You can also analyze network connections and event fanout.
To find processes with high mailbox latency on an Ergo node, you need to connect to the running Ergo Framework distributed system via MCP. This allows you to perform process state analysis and identify performance bottlenecks.
Your Ergo node keeps experiencing restart loops due to potential memory issues or stuck processes. You can analyze it by utilizing network inspection and process state analysis tools to diagnose the root cause of the production issue. Profiling tools help resolve these network problems and event fanout failures.
sanand0Control Chrome via DevTools Protocol for browser testing and debugging.
htlin222Profile Node.js, Python, and Go applications to identify performance bottlenecks.
ozan-fnConfigure structured logging, metrics, tracing, and profiling for Go services.
zm2231Diagnose software bugs through guided hypothesis testing and step-by-step fix verification.
