{
  "uid": "cogitave.learn.observability-and-reliability.introduction",
  "kind": "moduleUnit",
  "href": "/modules/observability-and-reliability/introduction/",
  "title": "Introduction",
  "summary": "",
  "type": null,
  "products": [],
  "roles": [],
  "levels": [],
  "subjects": [],
  "headings": [
    "Day-0 honesty",
    "What you will get from this module"
  ],
  "source": "You cannot manage what you cannot measure, and you cannot promise a reliability\nnumber you never observe. This final module of the path is about both halves:\nhow Cogitave **measures** a running system, and how it turns that measurement\ninto an **engineered** reliability discipline instead of a hope.\n\nThe two halves are owned by two standards, and they are deliberately kept\nseparate. The\n[observability standard](../../../../standards/docs/standards/observability.md)\nis the **measurement** layer - the telemetry spine (traces, metrics, logs) and\nthe SLI/SLO definitions. The\n[reliability standard](../../../../standards/docs/standards/reliability.md) sits\n**on top of it** and adds the engineering: how to set an SLO, how to alert on it,\nand the error-budget policy that decides when the team stops shipping. The\nprocess decision behind both is recorded in\n[ADR-0020](../../../../standards/docs/decisions/0020-reliability-and-secure-sdlc.md).\n\n> [!IMPORTANT]\n> Observability **defines** the SLIs, SLOs, and the freeze trigger; reliability\n> **engineers** the SLO, the burn-rate alerting, and the freeze policy behind\n> that trigger. Reliability consumes observability - it never restates SLI\n> definitions. Learn which standard owns what, and you will always know where to\n> look.\n\n## Day-0 honesty\n\nRead every rule here as **the spec each service conforms to as it is built**, not\na report on a running fleet. At Day 0 no service is in production, no SLO is being\nburned, and no pager has fired. \"The on-call engineer pages\" describes the\nspec'd behavior once a service is live and instrumented - not a claim that a\nrotation runs today. This matches how the rest of the estate reports itself\nhonestly: Yuva still marks live inference as MOCK and learning as DORMANT.\n\n## What you will get from this module\n\nA working command of the telemetry model - what a trace, a metric, and a log are\nin Cogitave and why they are bound to one queryable Core model - plus the\nvocabulary of reliability engineering: SLI, SLO, error budget, burn rate, and the\npolicy that gives an SLO teeth. By the end you should be able to instrument a\nservice and reason about whether it is reliable enough to keep shipping.\n",
  "partOf": "cogitave.learn.observability-and-reliability",
  "durationInMinutes": 4,
  "quiz": null
}