Exploring Capital One’s Open‑Source DevOps Dashboard Hygieia: Value, Features, Views, and Technical Details

In the previous article I discussed Capital One’s DevOps transformation principles and key technologies; here I focus on the open‑source DevOps dashboard Hygieia that Capital One developed and released.

During their agile and DevOps journey, Capital One moved from a "Closed Source First" mindset to an "Open Source First" approach, actively embracing and contributing to open‑source tools as a way to create better products and share benefits.

Now we will study Capital One’s open‑source DevOps dashboard tool, Hygieia.

1. Value of a DevOps Dashboard

We should "start with the end in mind"; before describing the dashboard’s specific functions, let’s discuss its value.

The DevOps Handbook proposes a three‑step method: (1) enable fast left‑to‑right flow of value by building a continuous delivery pipeline; (2) establish rapid, continuous right‑to‑left feedback; (3) foster continuous learning and experimentation. Hygieia concentrates on the second step, providing visual, real‑time feedback on the health of the delivery pipeline.

2. Main Functions of the Dashboard

Successful continuous delivery requires rapid feedback for everyone involved—product owners, developers, testers, operations, security engineers, release engineers, and managers. Transparency at each pipeline stage is crucial, especially in large organisations with many agile teams.

Using Hygieia, teams can see:

Which user stories are in progress or completed.

Code commit details, frequency, and authors.

Build status, failures, and root‑cause information.

Static analysis results, security scan outcomes, unit‑test coverage, functional and non‑functional test results.

Environment details and deployment status of code.

Which software version is deployed to which environment and any deployment failures.

Code movement across development, test, and integration environments.

Number of items waiting to move to the next stage, highlighting bottlenecks.

Hygieia presents a complete view from user story to production deployment, allowing product teams to take appropriate actions to fix issues.

The dashboard also shows quality metrics, helping product owners decide whether to schedule quality‑improvement work in the next sprint and prompting discussions about pipeline design, such as test execution time or slow processes.

Early adoption at Capital One revealed poor unit‑test coverage and many severe code issues; teams responded by adding improvement work to regular sprints, supported by management.

3. Main Views

Hygieia offers four primary views:

Composite View : detailed product information, including current sprint features, code commits, CI activity, code analysis, security analysis, test results, deployments, and environment status.

Pipeline View : lifecycle of each component from development through testing to deployment.

Product View : end‑to‑end lifecycle for each configured product.

Cloud Environment View : application instances, resource utilisation, and related data.

Below are key screenshots of these pages:

Code commit stage:

Commit details per stage:

Deployment stage:

Production stage:

Pipeline health view:

Pipeline view:

Cloud resources view:

Cloud resource details:

4. Technical Details

Architecture diagram:

Hygieia can integrate with a wide range of tools:

Requirement Management : Jira, VersionOne, Gitlab

Configuration Management : Bitbucket, GitHub, Gitlab, Subversion

Build Management : Bamboo, Jenkins, Jenkins‑codequality, Cucumber, Sonar

Deployment Management : uDeploy, XLDeploy

Environment Management : AWS

Performance Management : AppDynamics

CMDB : HP Service Manager (HPSM)

Library Policy : Nexus IQ

Artifact Repository : Artifactory

ChatOps : HipChat

Hygieia provides ready‑made collectors for each of these tools, making integration straightforward.

5. Summary

Peter Drucker once said, "If you can’t measure it, you can’t improve it."

DevOps is not a one‑time project; merely adding automation tools or a delivery pipeline does not guarantee efficiency or quality gains. The key is to obtain effective feedback across the entire delivery lifecycle, increase transparency, and continuously apply targeted improvements based on metrics.

Continuous learning and practice keep DevOps moving forward.

6. Hygieia Resources

Project repository: https://github.com/capitalone/Hygieia

Documentation: http://www.capitalone.io/Hygieia

Additional article: https://www.infoq.com/news/2016/03/hygieia