{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibpn7stoj22yn4jkr7qt77adl7im3dtarpqohmba4zkfkaqb53la4",
    "uri": "at://did:plc:gapzbf5nl5wxaqkqoecaeawh/app.bsky.feed.post/3mlx45zqjf3s2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreifxqkkewxd6lqxwrrdutfjzm5bra5q67e2bf7jz4am756ojspkjcu"
    },
    "mimeType": "image/webp",
    "size": 26328
  },
  "path": "/migration-observability-measure-meaning-not-movement/",
  "publishedAt": "2026-05-15T08:57:28.000Z",
  "site": "https://devops.com",
  "tags": [
    "Blogs",
    "Business of DevOps",
    "Contributed Content",
    "Observability",
    "Social - Facebook",
    "Social - LinkedIn",
    "Social - X",
    "control plane",
    "devops",
    "migration",
    "observability"
  ],
  "textContent": "Traditional operational observability focuses on latency, errors, throughput and saturation. Migration observability needs a different category: Semantic drift.",
  "title": "Migration Observability: Measure Meaning, Not Movement"
}