An operator who cannot see a service cannot diagnose it, change it safely or say when it has been restored. This chapter collects the tools for that seeing and for the promises that give it a meaning: the telemetry standards and collectors that carry signals, the records that state what users are promised, the alerts that call a person when the promise is at risk, the policy that keeps an AI correlation layer inside a noise budget, and the measures by which operations is judged. It serves the activity of observing a service and speaking about it with evidence, which AI Operations calls O1 Observe (10, Nordqvist, 2026).
All four kinds of tool occur here. The artefacts are the service record (SVC-*), the service level objective record (SLO-*), the alert-correlation policy (ACP-*) and its evaluation record (EVL-*), the metric definition catalogue (MET-*), the collector configuration and the alerting rules of AI Platform and Security, and two listings of Architecture as Code. The third-party tools are open standards and open-source software: OpenTelemetry, its semantic conventions for generative AI, OpenSLO, the Prometheus Operator Watchdog alert, and the research programme whose delivery metrics the series uses. The methods are burn-rate alerting, observability as code, the noise budget, the writing of an objective from a user journey, and the measures of patch velocity, shortcut rate and board reporting. Most of the tools come from AI Operations (Book 10), which defines the objective and correlation artefacts; AI Platform and Security (Book 3) supplies the AI-specific telemetry and alerting; Architecture as Code (Book 1) supplies the infrastructure and delivery metrics; and Books 2, 5, 6, 7, 8 and 9 contribute a method or a standard each.
The chapter follows that path. It begins with telemetry and standards, then the records that fix objectives, then alerting, then the policy for correlation, and ends with measurement. As in the other chapters of Parts II to VII, each principal tool has an entry in a fixed format, minor tools are named in family tables, and the closing paragraphs account for the inventory. Statements about third-party software cite its own documentation or standard; the earlier volumes are cited only for what the series defines and concludes.
Primary topics explored
- Telemetry and standards
- Service and objective records
- Alerting and burn rates
- Correlation policy and noise budget
- Measurement
- Across the usage modes
About Tools
Tools is a companion to The Transformed Architecture. It collects the tools that Books 1 to 10 describe in one reference, organised by what the practitioner is doing: artefacts (templates, manifests, records), own tools, third-party tools and standards, and methods. Each entry says what a tool is for, when to use it, what it needs and produces, and where the book that defines it explains the reasoning. The book covers choosing, adopting and retiring tools, architecture and delivery, governing AI, securing and testing, operating, agents and autonomy, and people, organisation and society, for European enterprises and public authorities. It comes with a template library, an inventory, three web tools and the Toolbox Maturity Method.
It builds on the conclusions of Architecture as Code, AI Governance, AI Platform and Security, AI Red Team, AI Threat, The Transformed Security Architect, AI Boss, AI Blue, AI Purple and AI Operations.
Architects and security architects, CIOs and CISOs, platform and operations leads, heads of governance, risk, compliance and third-party risk, AI governance and AI platform teams, red, blue and purple team leads, boards and management bodies, procurement and vendor managers, supervisors and auditors, works councils and unions, data protection officers, and public-sector leaders.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Chapter 15: Observability and Service Objective Tools in Tools gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Operating” and is one of 29 drawn from the manuscript.