Skip to content
forked from causaai/causa

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

 
 

Repository files navigation

Causa AI Agent

Automated, intelligent root-cause analysis for Java Anomalies in Kubernetes.

Explore The Docs · API Specifications · Tunables · Report Bug · Request Feature


Contributors Forks Stargazers Issues License


Table of Contents

  1. About The Project
  2. Why Causa?
  3. Getting Started
  4. Contributing
  5. License
  6. Contact

About The Project

Causa is an AI-powered root cause analysis agent that helps engineering teams reduce Mean Time to Resolution (MTTR) for Java issues on Kubernetes and virtual machines.

When a Prometheus Alertmanager alert is triggered, Causa automatically collects production context—including application logs, pod health, Kubernetes events, and infrastructure insights via MCP servers—and uses AI to identify the root cause. Within minutes, it delivers prioritized remediation steps, covering both immediate mitigation and long-term fixes, so engineers can resolve incidents faster with less manual investigation.

Instead of engineers manually collecting data from multiple tools, Causa delivers a complete diagnosis and recommended next actions, enabling teams to resolve production incidents faster, minimize downtime, and improve service reliability.

Built With

Quarkus Java PostgreSQL LangChain4J

Key Features

  • 🚨 Automated Incident Response – Responds instantly to Prometheus Alertmanager memory alerts with no manual intervention.

  • 🔍 AI-Powered Root Cause Analysis – Correlates logs, metrics, Kubernetes events, and runtime information to identify the root cause.

  • ⚡ Reduce MTTR – Delivers prioritized remediation steps, including immediate mitigation and long-term fixes, within minutes.

  • 🧠 Context-Aware Diagnostics – Automatically gathers production context from Kubernetes, JVM, Kruize Recommendations and infrastructure through MCP servers.

  • ☸️ Kubernetes & VM Support (Planned) – Diagnoses Java issues across both Kubernetes clusters and traditional virtual machine deployments (VM Support is planned for next release).

  • 🤖 Flexible LLM Providers – Supports multiple AI backends including Anthropic Claude, Vertex AI Claude, with extensible support for IBM Bob (Planned) and Ollama (Planned).

  • ⚙️ Dynamic Configuration – Update operational settings securely without restarting the application.

(back to top)


Why Causa?

Manual Incident Response With Causa 🚀
Engineer waits for an alert and starts investigating manually. Automatically responds to Prometheus Alertmanager alerts.
Switches between Grafana, kubectl, logs, JFR, and monitoring dashboards. Collects logs, Kubernetes events, JFR (Planned), JVM metrics (Planned), and infrastructure context automatically.
Correlates data across multiple tools manually. AI correlates all production context into a single diagnosis.
Requires JVM and Kubernetes expertise to identify the root cause. AI identifies the most likely root cause with supporting evidence.
Engineers spend hours debugging memory leaks, OOMKills, and GC issues. Root cause analysis is completed in minutes, reducing MTTR.
Team decides what to do next under pressure. Provides prioritized remediation steps with immediate mitigation and permanent fixes.
Knowledge stays with individual engineers. Every incident follows a consistent, repeatable investigation workflow.
High operational overhead during production incidents. Faster incident resolution, less downtime, and improved reliability.

(back to top)


Getting Started

Prerequisites

Requirement Minimum Version Notes
Java (JDK) 21 OpenJDK or compatible
Apache Maven 3.9+ or use ./mvnw
Docker / Podman any recent for container image builds
PostgreSQL 14+ must have pgvector installed
Kubernetes MCP Server latest pod status, logs, events via JSON-RPC 2.0
Kruize MCP Server latest resource cost & performance recommendations
kubectl + kustomize 1.27+ / 5+ for Kubernetes deployment

Running in Dev Mode

Dev mode enables live-code reload and autowires Quarkus Dev Services — Postgres instance must be deployed to run application in dev mode.

./mvnw compile quarkus:dev
# or
quarkus dev

Dev UI is available at http://localhost:8080/q/dev/.

Health Endpoint is available at http://localhost:8080/api/v1/healthz.

Alert Webhook Endpoint is available at http://localhost:8080/api/v1/healthz.

The dev profile defaults to dev_password for the DB password and vertex-ai-anthropic for the LLM provider. Override via environment variables before starting in application.yaml

Packaging

# Fast-JAR (default)
./mvnw package
java -jar target/quarkus-app/quarkus-run.jar

# Über-JAR
./mvnw package -Dquarkus.package.jar.type=uber-jar
java -jar target/*-runner.jar

(back to top)


Contributing

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

(back to top)


License

Distributed under the Apache 2.0 License. See LICENSE for more information.

(back to top)


Contact

Project Link: https://github.com/causaai/causa

(back to top)

Built with ❤️ by the Causa Team

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages