FAQ

Q: What does RCA really mean?
A: Different people expect different things from Root Cause Analysis (RCA). Some want RCA to pinpoint issues at the code level, while others expect it to highlight the infrastructure or resource layer.

Q: How is your approach to RCA different?
A: We focus on the current fault condition. Instead of tracing endlessly, we identify the direct reason the system is failing right now.

Q: What kinds of issues can you detect?
A: Our detection covers three major categories:

• Errors

  • Extracted directly from logs to reflect application and service errors.

• Slowdowns

  • Using eBPF data to detect:
    • Disk I/O saturation
    • Lock contention
    • Network bottlenecks
    • Thread scheduling delays
    • Code-level issues such as excessive loops or repeated traversals

• Resource Problems

  • CPU, memory, disk, and file descriptors
  • Identify the top resource consumers and compare their TPS (throughput) against resource usage to see if consumption is reasonable or abnormal

Q: What value does this bring to users?
A: By providing immediate, actionable insight into what is actually breaking, teams can respond faster, reduce downtime, and resolve most real-world incidents without unnecessary complexity.