Champa Health Monitor v2.0: From What’s Broken? to Why & How to Fix It

Remember debugging Camunda incidents at 3 AM, jumping between logs, database queries, and Cockpit tabs trying to figure out what went wrong?

V2.0 just made that a lot easier.

We’ve added AI-powered incident intelligence that doesn’t just show you what’s broken - it tells you why, shows you patterns, and recommends what to do about it.

:movie_camera: See It In Action

Youtube Full Demo: Camunda Health Monitor v2.0 Open Source - AI-Powered Monitoring with Incident Intelligence

:sparkles: What’s New

Incident Intelligence Center - Click any incident, see root cause, historical patterns, affected instances, and specific remediation steps. All in one view.

Weekly Load Patterns - AI-powered heatmaps showing exactly when your cluster is busy. Finally know the right time to schedule that deployment.

ML Analytics - Capacity forecasting, stuck activity detection, bottleneck ROI calculations. Know what will break before it breaks.

Process Categorization - Automatic grouping by speed. Perfect for SLAs and architectural planning.

and many more…

:spouting_whale: Try It Now

GitHub: GitHub - bibacrm/camunda-health-monitor: Lightweight monitoring dashboard for Camunda 7 clusters with real-time metrics, JVM health tracking, and database analytics. Built with Flask, Alpine.js, and Tailwind CSS. · GitHub
Docker Hub: champabpmn/camunda-health-monitor - Docker Image


:speech_balloon: I’d Love Your Feedback

What would make this indispensable for your team?

  • Different metrics?
  • Integration with a specific monitoring stack?
  • Something else?

Drop a comment - every suggestion helps shape the roadmap.

This looks really useful, especially for troubleshooting incidents under pressure. The root-cause analysis and historical pattern detection could save a lot of time compared with jumping between logs and database queries. Integration with Prometheus and Grafana, along with alerts for recurring failures, would make it even more valuable. Great work on making this open source!

Prometheus/Grafana integration would be most useful if the alert payload already includes the incident summary, likely root cause, affected process/instance count, and a deep link back to the relevant view. That avoids turning every anomaly into a dashboard visit. For recurring failures, grouping related alerts by process definition or activity could also reduce noise.