https://minuk.dev/opampcommander/docs/configuration/Recent content in Configuration on OpAMP CommanderHugoen-ushttps://minuk.dev/opampcommander/docs/configuration/collector-opamp/Mon, 01 Jan 0001 00:00:00 +0000https://minuk.dev/opampcommander/docs/configuration/collector-opamp/<p>Commander serves OpAMP WebSocket and HTTP traffic at <code>/api/v1/opamp</code>. Choose the connection topology according to the capabilities you need. The configurations below target Collector Contrib <strong>0.163.1</strong> (Contrib components 0.163.0) and Supervisor <strong>0.163.0</strong>. Collector 0.163.1 fixes the 0.163.0 distribution release.</p> <table> <thead> <tr> <th>Deployment</th> <th>Behavior</th> </tr> </thead> <tbody> <tr> <td>Collector with the OpAMP extension connected directly</td> <td>Reports description, health, effective config and available components. Does not accept remote configuration.</td> </tr> <tr> <td>Supervisor connected to Commander, with a managed Collector</td> <td>Applies remote configuration when <code>accepts_remote_config</code> is enabled; reports its status and can restore a last-working configuration. Supervisor injects the Collector&rsquo;s local OpAMP connection.</td> </tr> </tbody> </table> <h2 id="direct-extension">Direct extension</h2> <p>From the repository root, use <code>scripts/opampextension-ws.yaml</code> or <code>scripts/opampextension-http.yaml</code>. These examples target Commander on the Docker host; replace <code>host.docker.internal</code> with <code>localhost</code> when running natively.</p>