[OpAMP] Update OpAMP port by RassK · Pull Request #4374 · open-telemetry/opentelemetry-dotnet-contrib (original) (raw)
Merged
merged 10 commits into
May 19, 2026
Conversation
Design discussion issue open-telemetry/opamp-spec#323
Changes
Changes OpAMP port from 3418 to 3420
Merge requirement checklist
- CONTRIBUTING guidelines followed (license requirements, nullable enabled, static analysis, etc.)
- Unit tests added/updated
- Appropriate
CHANGELOG.mdfiles updated for non-trivial changes - Changes in public API reviewed (if applicable)
3 tasks
Co-authored-by: Martin Costello martin@martincostello.com
This was referenced
May 14, 2026
…y-dotnet-contrib into opamp-port
Conflicts:
src/OpenTelemetry.OpAmp.Client/CHANGELOG.md
| message OpAMPConnectionSettings { |
|---|
| // OpAMP Server URL This MUST be a WebSocket or HTTP URL and MUST be non-empty, for |
| // example: "wss://example.com:4318/v1/opamp" |
| // example: "wss://example.com:4320/v1/opamp" |
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that it could be reverted and bringed together with v0.18.0.
Not a blocker.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My original idea was to have all places fixed, so a concrete version (commit, tag, etc) does not provide different information about ports.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})