{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigty7kac4sswhpfpefk53r4uxzpthqhndcanh65xswihpetzv5lze",
    "uri": "at://did:plc:smygvncmizyew64c5cqjs4lp/app.bsky.feed.post/3mj7gfmx4uhi2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreieyjkd5b5rujtwgm45kl4eygirphaxz55ochgbaztwwqa36d57dra"
    },
    "mimeType": "image/png",
    "size": 4080948
  },
  "path": "/blog/moving-beyond-supports-opentelemetry-why-there-s-a-need-for-a-shared-maturity-model",
  "publishedAt": "2026-04-10T07:23:00.000Z",
  "site": "https://dash0.com",
  "textContent": "\"Supports OpenTelemetry\" means something different for every project. In this post, we look at why the ecosystem needs a shared maturity model to help projects mature their integrations, for the benefit of both users and maintainers.",
  "title": "Moving Beyond “Supports OpenTelemetry”: Why There’s a Need for a Shared Maturity Model"
}