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
This issue tracks the support and design of a distribution proposal.
Proposal:
Create a distribution of the collector that is meant for use as a gateway, a process able to listen for data in various protocols, process it and export in OTLP.
This distribution doesn't run any background process such as scrapers, it should only use resources based on the volume of data transiting through the collector.
wondering if it makes more sense, given that many customers already build custom collectors, if we should consider having "example distributions" with a folder full of manifests for suggested configurations, without having to produce several more artifacts on each release for new distributions.
This issue tracks the support and design of a distribution proposal.
Proposal:
Create a distribution of the collector that is meant for use as a gateway, a process able to listen for data in various protocols, process it and export in OTLP.
This distribution doesn't run any background process such as scrapers, it should only use resources based on the volume of data transiting through the collector.
Proposed manifest:
The text was updated successfully, but these errors were encountered: