Originally reported by Container Journal. Published January 2020.
What Is Astro?
Fairwinds, a managed Kubernetes services provider, released an open source project called Astro that creates a simplified, automated bridge between Kubernetes clusters and the Datadog monitoring platform. The project is aimed at operations teams that already rely on Datadog to monitor traditional monolithic applications and want to extend that same tooling to their Kubernetes workloads without rebuilding their monitoring workflows from scratch.
The Problem Astro Solves
According to Fairwinds CTO E.J. Etherington, one of the most common pain points for Datadog users running Kubernetes is that monitors are typically configured and deployed manually. As clusters scale and Kubernetes objects change — new deployments, namespaces, services — each corresponding Datadog monitor must be manually updated to stay accurate. This creates significant operational overhead and increases the risk of gaps in monitoring coverage.
Astro addresses this by automating monitor lifecycle management. Rather than requiring a site reliability engineer (SRE) to track changes in Kubernetes and reconcile them with Datadog configuration, Astro handles this automatically using rule sets based on defined patterns within Kubernetes.
How Astro Works
Astro operates at the Kubernetes namespace level. Its core capabilities include:
- Automated monitor management: Astro watches Kubernetes objects within a namespace and keeps corresponding Datadog monitors in sync as those objects change.
- Dynamic updates: When a Kubernetes object is modified — for example, a deployment is scaled or a new service is added — Astro updates the associated Datadog monitor automatically to reflect the current state.
- Contextualized alerting: Data from managed Kubernetes objects can be injected directly into Datadog monitor definitions, enriching alerts with contextual metadata. This makes it easier for on-call engineers to triage incidents without having to cross-reference multiple sources.
- Rule-based pattern matching: Monitors are created and managed based on defined rules tied to patterns in Kubernetes resource definitions, giving teams a consistent and repeatable way to enforce monitoring standards across clusters.
The end goal, as Etherington described it, is to eliminate the manual integration work that would otherwise fall to an SRE every time a Kubernetes environment changes.
Why Datadog, When Prometheus Exists?
Prometheus is the most widely adopted open source monitoring tool in Kubernetes-native environments. As a CNCF project, it integrates deeply with the cloud-native ecosystem and is a natural default for teams building greenfield microservices architectures.
However, many enterprise IT operations teams have already standardized on Datadog for production application monitoring — often years before they began adopting Kubernetes. Migrating away from an established monitoring platform is costly and disruptive. Astro is designed for exactly this scenario: organizations that have real-world Kubernetes workloads in production but need those workloads to feed into the same Datadog dashboards and alert pipelines used for everything else in their environment.
Etherington noted that Datadog is capable of ingesting metrics from a wide variety of open source and commercial software sources, making it a practical aggregation layer for heterogeneous environments.
Fairwinds’ Open Source Ecosystem
Astro is not Fairwinds’ first open source contribution to the Kubernetes community. The company also maintains:
- Polaris: A configuration validation tool for Kubernetes that checks deployments against best practices and security policies.
- Goldilocks: A utility that helps teams right-size Kubernetes resource requests and limits by analyzing actual resource usage, reducing both over-provisioning and out-of-memory incidents.
All three projects emerged from practical problems Fairwinds encountered while operating managed Kubernetes services for its customers. This grounding in real operational experience gives the tools a pragmatic focus that distinguishes them from more theoretical tooling.
The Broader Observability Challenge in Kubernetes
As Kubernetes adoption moves from experimentation to production at scale, the demand for robust, automated observability tooling continues to grow. Microservices architectures introduce complex dependency chains that make monitoring not just useful but essential. A failure in one service can cascade across many others, and without comprehensive observability, identifying root causes becomes extremely difficult.
Historically, IT operations teams applied monitoring selectively — prioritizing mission-critical monolithic applications due to tooling costs and complexity. That approach does not translate well to Kubernetes environments where dozens or hundreds of interdependent services may be running simultaneously.
Projects like Astro represent one approach to bridging the gap: rather than forcing teams to choose between their existing monitoring investment and Kubernetes-native tooling, they automate the integration so both can coexist without placing additional manual burden on already-stretched SRE and operations teams.
Key Takeaways
- Astro automates the creation and lifecycle management of Datadog monitors based on the state of Kubernetes objects.
- It is particularly valuable for teams already invested in Datadog who are expanding into Kubernetes without wanting to maintain two separate monitoring workflows.
- Monitors are kept continuously updated as Kubernetes namespaces and objects change, reducing manual SRE overhead.
- Fairwinds has open-sourced Astro alongside its Polaris and Goldilocks projects, all targeting real operational problems in managed Kubernetes environments.