https://hummingbird-project.io/docs/adrs/ Recent content in Architecture Decision Records on Project Hummingbird Hugo en https://hummingbird-project.io/docs/adrs/0001-unified-observability-stack/ Mon, 01 Jan 0001 00:00:00 +0000 https://hummingbird-project.io/docs/adrs/0001-unified-observability-stack/ <ul> <li><strong>Status:</strong> Proposed</li> <li><strong>Date:</strong> 2026-07-19</li> <li><strong>Author:</strong> Robert Sturla</li> <li><strong>Jira:</strong> <a href="https://redhat.atlassian.net/browse/HUM-4790" target="_blank">HUM-4790</a> (Epic), <a href="https://redhat.atlassian.net/browse/HUM-4791" target="_blank">HUM-4791</a> (Design task)</li> </ul> <h2 id="context">Context<a class="td-heading-self-link" href="#context" aria-label="Heading self-link"></a></h2> <p>Hummingbird has no single place to view the health of builds, infrastructure, and services. Multiple disconnected monitoring and alerting implementations exist — CloudWatch dashboards, custom forwarder Lambdas (cloudwatch-log-forwarder), ad-hoc SNS topics (hummingbird-events-topic), and per-service custom dashboards. Workloads span multiple clusters (MPP, ITUP.stable) with no cross-cluster visibility. This creates blind spots, duplicated effort, and inconsistent alerting behaviour.</p>