Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Continuous service discovery (#5363)
This change introduces a new way of how the discovery mechanism works. Instead of observing data for the first 10 seconds and creating a static receiver_cretor config from that, it'll be running discovery receiver watching for all supported receivers. Once a new endpoint for any supported service is available, the collector will try to fetch metrics from it. If the collector cannot get metrics from a new service right away, it'll send detailed information about what can be done to enable it to the backend, which will be reflected in the newly discovered services UI. Any services that are successfully discovered will also be reflected in the UI. The collector sends entity events as OTLP logs to deliver information about the discovered services. The new functionality can be enabled with "splunk.continuousDiscovery" feature gate by adding --feature-gates=splunk.continuousDiscovery argument to the otecol command.
- Loading branch information