Skip to content

[9.3] (backport #12857) Add opampextension to EDOT Collector#12876

Merged
ycombinator merged 2 commits intoelastic:9.3from
ycombinator:edot-add-opamp-ext
Feb 20, 2026
Merged

[9.3] (backport #12857) Add opampextension to EDOT Collector#12876
ycombinator merged 2 commits intoelastic:9.3from
ycombinator:edot-add-opamp-ext

Conversation

@ycombinator
Copy link
Copy Markdown
Contributor

What does this PR do?

Adds opampextension as a Core component to the EDOT Collector (internal/edot).

Changes:

  • Added github.com/open-telemetry/opentelemetry-collector-contrib/extension/opampextension v0.145.0 as a direct dependency in go.mod
  • Registered opampextension.NewFactory() in the EDOT Collector's extension factory list (otelcol/components.go)
  • Marked opampextension as a Core component in components.yml
  • Updated golden files (components-output.yml and components-output-fips.yml) to include the opamp extension entry (stability: Alpha)
  • Updated go.sum and NOTICE.txt/NOTICE-fips.txt via go mod tidy and mage notice

Why is it important?

The OpAMP (Open Agent Management Protocol) extension enables the EDOT Collector to communicate with an OpAMP server for remote management and configuration. This will allow Fleet Server to monitor and manage EDOT Collector via OpAMP.

Checklist

  • I have read and understood the pull request guidelines of this project.
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

No disruptive impact. This adds a new optional extension to the EDOT Collector; existing configurations are unaffected.

How to test this PR locally

Run the EDOT Collector and verify the opamp extension is listed:

elastic-agent otel components | grep opamp

Related issues

Questions to ask yourself

  • How are we going to support this in production? The opampextension is an upstream OTel Contrib component maintained by the OTel community.
  • How are we going to measure its adoption? Via configuration usage telemetry.
  • How are we going to debug this? Standard OTel Collector logging applies; the extension exposes its own status via the health check mechanism.

@ycombinator ycombinator requested a review from a team as a code owner February 20, 2026 14:03
@ycombinator ycombinator requested review from blakerouse and michel-laterman and removed request for a team February 20, 2026 14:03
@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

cc @ycombinator

@ycombinator ycombinator merged commit bd4958a into elastic:9.3 Feb 20, 2026
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants