https://minuk.dev/opampcommander/docs/Recent content in Documentation on OpAMP CommanderHugoen-ushttps://minuk.dev/opampcommander/docs/api-stability/Mon, 01 Jan 0001 00:00:00 +0000https://minuk.dev/opampcommander/docs/api-stability/<p>This policy covers the public REST API under <code>/api/v1</code>, represented by <code>pkg/apiserver/docs/swagger.yaml</code>, and the exported Go API in <code>pkg/client</code>. Internal packages, alpha or experimental features explicitly documented as such, and the OpAMP protocol endpoint are outside this policy.</p> <p>The REST API and Go client are versioned together with OpAMP Commander; the client does not have an independent version.</p> <h2 id="compatibility-promise">Compatibility promise</h2> <p>OpAMP Commander follows <a href="https://semver.org/">Semantic Versioning</a>:</p> <ul> <li>Patch releases preserve backward compatibility.</li> <li>Before <code>v1.0.0</code>, a minor release may contain a previously announced breaking change. After <code>v1.0.0</code>, breaking changes require a major release.</li> <li>Adding an optional endpoint, field, parameter, or exported Go symbol is backward-compatible. Removing or renaming one, changing its type or meaning, or making an optional input required is breaking.</li> </ul> <p>The OpenAPI CI check blocks pull requests that remove or incompatibly change the committed REST contract. An intentional breaking change requires a documented migration and an explicit maintainer override. Go client compatibility is reviewed as part of changes to exported <code>pkg/client</code> symbols.</p>https://minuk.dev/opampcommander/docs/opamp-conformance/Mon, 01 Jan 0001 00:00:00 +0000https://minuk.dev/opampcommander/docs/opamp-conformance/<p>This page tracks how much of the <a href="https://opentelemetry.io/docs/specs/opamp/">OpAMP specification</a> OpAMP Commander implements today. It is a living document; update it whenever the OpAMP message handling changes.</p> <p><strong>Legend:</strong> ✅ Supported · 🟡 Partial · ⛔ Intentionally not advertised / not implemented. Supported means the described server path exists, not that every collector implements it or that every normative requirement has an interoperability test. Planned work is not counted as support.</p> <p>Capability inventory: all seven nonzero server flags and sixteen nonzero agent flags in <a href="https://opentelemetry.io/docs/specs/opamp/#agenttoservercapabilities">the OpAMP specification</a> and the repository&rsquo;s pinned <strong>opamp-go v0.25.0</strong>. The <code>Unspecified</code> zero values mean no capabilities, not an extra feature. Implementation reviewed at <code>6905470c5</code>.</p>