Creating a build a monitoring architecture for our CI/CD pipelines to transform scattered Jenkins build data into actionable insights

HaloDoc is a healthcare technology platform that offers telemedicine services, online pharmacy, and health information resources to users in Indonesia. Through its platform, HaloDoc aims to improve access to healthcare services, empower patients to take control of their health, and facilitate collaboration between healthcare providers. Developers can learn from HaloDoc's innovative use of technology to address healthcare challenges, leveraging telemedicine, artificial intelligence, and data analytics to enhance patient care and outcomes.

Halodoc

Halodoc's engineering team built a custom CI/CD monitoring system to address the lack of visibility across hundreds of daily Jenkins builds. Instead of relying on Jenkins plugins, they export structured build metadata (status, duration, failure category, service name, environment, etc.) into a centralized MySQL database after each pipeline execution. Grafana dashboards visualize trends like success/failure ratios and unstable pipelines, while weekly automated reports give leadership a high-level view of CI health. A key innovation is structured failure categorization (Validation, Security, Build, Deployment, etc.) that transforms raw failure logs into actionable insights. The system also integrates with an internal MCP-based copilot for natural language build queries. After implementation, production build success rate improved from 70% to 92%.

Turning CI Noise into Insights: Our Build Monitoring Architecture

The Problem: CI/CD Visibility Was Fragmented