02 — Capability · BC-730.60
Infrastructure Automation & Observability
Define infrastructure in code, provision it through pipelines and watch it through shared telemetry, so the platform is consistent, auditable and visible to the teams that depend on it.
- Infrastructure as Code
- Platform Automation
- Monitoring Services
In scope
- Infrastructure as code and configuration management
- Shared observability tooling and standards
- Platform service catalog for internal consumers
- Automation runbooks and self-healing
Out of scope
- Application-level monitoring thresholds (see BC-720)
- Internal developer platform for a software product business (see BC-1210)
Realized by · 1
Used in · 2
Build it · 8
- pattern Immutable Infrastructure via BC-730.60.10
- pattern Infrastructure as Code via BC-730.60.10
- pattern Distributed Tracing via BC-730.60.30
- pattern Structured Logging via BC-730.60.30
- stack Open observability stack via BC-730.60.30
- stack Platform infrastructure baseline via BC-730.60.10
- book Infrastructure as Code
- book Observability Engineering
Decomposes into · 4
- BC-730.60.10Infrastructure as CodeDescribe environments declaratively and build them from that description, so drift is detectable and rebuilds are routine.
- BC-730.60.20Configuration ManagementEnforce the intended configuration of servers and services continuously and correct what wanders from it.
- BC-730.60.30Observability PlatformOperate the shared logging, metrics and tracing services and set the standards for what every workload must emit.
- BC-730.60.40Platform Service CatalogPackage common infrastructure needs as orderable services with clear options, so teams request outcomes instead of parts.