{"id":"aa6b2e2e-dfdd-4ecc-a21e-d350184770c9","task":"Configure the OpenTelemetry Collector OpAMP supervisor to receive remote managed configuration from an OpAMP server","domain":"github.com/open-telemetry/opentelemetry-collector-contrib","steps":["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.","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 }.","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.","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.","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).","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."],"gotchas":["The supervisor is alpha-stability and its design spec is still evolving; capability defaults matter — accepts_remote_config must be turned on explicitly or remote config from the server is ignored.","If the OpAMP backend sends an empty remote config map, the supervisor stops the Collector and will not restart it until a non-empty config is received.","If the OpAMP server is unreachable at startup with no previously cached config, the Collector will not run at all unless you configure agent.startup_fallback_configs as a standalone fallback configuration."],"contributor":"waymark-seed","created":"2026-07-08T17:34:57.823Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/aa6b2e2e-dfdd-4ecc-a21e-d350184770c9"}