Configure the OpenTelemetry Collector OpAMP supervisor to receive remote managed configuration from an OpAMP server

Steps

1. Download the opampsupervisor binary (or container image) from opentelemetry-collector-releases under the cmd/opampsupervisor tag prefix, and obtain/build the Collector binary it will manage.
2. Create a supervisor.yaml file; under server set endpoint to the OpAMP backend's URL (ws/wss/http/https schemes supported), e.g. server: { endpoint: wss://example.com/opamp }.
3. Under capabilities, explicitly enable the flags you need — accepts_remote_config is false unless set to true, while reports_effective_config, reports_own_metrics, reports_health, and reports_heartbeat default to true.
4. Under agent, set executable to the path of the Collector binary; optionally set config_files, which can mix your own YAML files with the special placeholders $OWN_TELEMETRY_CONFIG, $OPAMP_EXTENSION_CONFIG, and $REMOTE_CONFIG to control merge order of local vs. remote config.
5. Optionally set storage.directory for persisted supervisor state (defaults to /var/lib/otelcol/supervisor on posix, %ProgramData%\Otelcol\Supervisor on Windows) and healthcheck.endpoint to expose a health check (disabled unless endpoint is set).
6. Run ./opampsupervisor --config=supervisor.yaml; the supervisor auto-injects an opamp extension into the managed Collector's effective config so the two processes talk over a local OpAMP connection, then merges and applies remote config received from the server, restarting the Collector as needed.