[{"data":1,"prerenderedAt":99},["ShallowReactive",2],{"navigation":3,"topic-observability":14,"topic-observability-ventures":75,"topic-observability-oss":76,"topic-observability-posts":98},[4],{"title":5,"path":6,"stem":7,"children":8,"page":13},"Blog","\u002Fblog","blog",[9],{"title":10,"path":11,"stem":12},"Kubernetes 101","\u002Fblog\u002Fkubernetes-introduction","blog\u002Fkubernetes-introduction",false,{"id":15,"title":16,"body":17,"description":61,"draftNotice":62,"extension":63,"meta":64,"navigation":62,"order":65,"path":66,"pillar":67,"related":68,"seo":72,"stem":73,"__hash__":74},"topics\u002Ftopics\u002Fobservability.md","Observability",{"type":18,"value":19,"toc":53},"minimark",[20,24,29,32,36,39,43,46,50],[21,22,23],"p",{},"A distributed application watching a critical manufacturing process across a hundred hosts generates enormous amounts of telemetry and, usually, very little understanding.",[25,26,28],"h2",{"id":27},"which-metrics-earn-their-storage","Which metrics earn their storage",[21,30,31],{},"Most metrics are collected because collecting them was easy. Cardinality is a budget, and spending it without a decision in mind is how observability bills get out of control.",[25,33,35],{"id":34},"tagsets-across-independent-modules","Tagsets across independent modules",[21,37,38],{},"The moment more than one team emits telemetry, labels drift. Enforcement has to happen at ingestion or at CI — asking politely does not work at scale.",[25,40,42],{"id":41},"the-missing-spans","The missing spans",[21,44,45],{},"Industrial systems trace almost nothing. A camera triggers, inference runs, a result reaches a display, and the only evidence is three unrelated metrics. End-to-end latency is a span problem, and treating it as a metrics problem is why bottlenecks stay invisible.",[25,47,49],{"id":48},"instrumenting-the-whole-chain","Instrumenting the whole chain",[21,51,52],{},"What it took to instrument camera to inference to display, and what surfaced immediately once the chain was visible.",{"title":54,"searchDepth":55,"depth":55,"links":56},"",2,[57,58,59,60],{"id":27,"depth":55,"text":28},{"id":34,"depth":55,"text":35},{"id":41,"depth":55,"text":42},{"id":48,"depth":55,"text":49},"Industrial systems are all metrics and no traces. Cost-controlled OpenTelemetry, tagset governance across independent modules, and knowing which signals earn their storage.",true,"md",{},3,"\u002Ftopics\u002Fobservability","observability",{"oss":69},[70,71],"opentelemetry","opamp",{"title":16,"description":61},"topics\u002Fobservability","dTp_hinKxNWnB_kT2iwSyoTSugoq5xC5ZLtNZD9xcTc",[],[77,89],{"id":78,"description":79,"extension":80,"featured":13,"language":81,"meta":82,"name":83,"order":65,"repo":84,"role":85,"slug":71,"stem":86,"why":87,"__hash__":88},"oss\u002Fwork\u002Foss\u002Fopamp.yml","Open Agent Management Protocol — remote configuration, health reporting and upgrade of telemetry agents at fleet scale.","yml","Go",{},"OpAMP","https:\u002F\u002Fgithub.com\u002Fopen-telemetry\u002Fopamp-go","watching","work\u002Foss\u002Fopamp","Managing a hundred collectors by hand is not a strategy. OpAMP is the piece that makes edge telemetry operable rather than merely deployed.","yon4Ya3Wd3NuC-tEujMUHya62K2hZiVWyKH143JdbWw",{"id":90,"description":91,"extension":80,"featured":13,"language":81,"meta":92,"name":93,"order":55,"repo":94,"role":85,"slug":70,"stem":95,"why":96,"__hash__":97},"oss\u002Fwork\u002Foss\u002Fopentelemetry.yml","The vendor-neutral standard for traces, metrics and logs.",{},"OpenTelemetry","https:\u002F\u002Fgithub.com\u002Fopen-telemetry","work\u002Foss\u002Fopentelemetry","Every observability argument I make assumes a signal format that outlives the tool consuming it. Industrial systems change vendors far more often than they change physics.","QOtHP5rFwrPxf1ddcxyJ6qkHquIZGNOtcX1Bru_xXnw",[],1791414106418]