The document an observability rollout should start from. A fixed scope engagement that produces a plan the platform team can execute and the operations team can read.
What it covers
How it runs
Discovery from existing inventories, architecture material and interviews with the platform and application teams. Design validated against reference workloads in the lab where a pattern needs testing. A written blueprint, reviewed with the client, and a walkthrough with the team that will execute it. Fixed scope, fixed duration, agreed before the work starts.
Who it is for
The Blueprint is the productised form of our instrumentation design and log strategy practices.
Questions
No. It is written in terms of coverage tiers, agent and gateway layout and log rules, which apply to any modern observability platform. Where a platform has a specific constraint the blueprint notes it.
The client’s platform team, a delivery partner of their choosing, or C4C with a delivery partner. The blueprint is written so that any of the three can pick it up.
Existing inventories, architecture material, access to the platform and application teams for interviews, and a view of the change windows the rollout will have to fit.
An hour with the practice, no slides, no obligation. Bring your incident history and your tooling list. Leave with a plain view of where your observability is working, where it is not, and what to do first.
Book an observability sense check