You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The OpAMP Supervisor needs to create a no-op pipeline to start the Collector with just the OpAMP extension during the bootstrapping process. Most existing components are not universally-present or have some issue (e.g. they bind to a port) that makes them non-ideal.
Describe the solution you'd like
The best components to use here are the nopexporter and noprecevier, which are lightweight, won't stop the Collector from starting, don't require special configuration, and should not be difficult to include in a distro. Switch the Supervisor's bootstrap config to use these components instead of the current components used in the no-op pipeline.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
**Description:** <Describe what has changed.>
Switch the Supervisor's bootstrap config to use nopreceiver and
nopexporter
**Link to tracking Issue:** #32455
---------
Co-authored-by: Evan Bradley <[email protected]>
Component(s)
cmd/opampsupervisor
Is your feature request related to a problem? Please describe.
The OpAMP Supervisor needs to create a no-op pipeline to start the Collector with just the OpAMP extension during the bootstrapping process. Most existing components are not universally-present or have some issue (e.g. they bind to a port) that makes them non-ideal.
Describe the solution you'd like
The best components to use here are the nopexporter and noprecevier, which are lightweight, won't stop the Collector from starting, don't require special configuration, and should not be difficult to include in a distro. Switch the Supervisor's bootstrap config to use these components instead of the current components used in the no-op pipeline.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: