[beats receivers] Do not require explicit configuration of the otelconsumer output #47656
Description
Removing the otelconsumer output is not straight forward, so while we experiment with alternative ways to get the behavior we want, let's not require explicitly defining it in configuration.
This will make it an implementation detail and ensure we are free to change and iterate on the internal structure of the beat receiver pipeline. We should do this before we begin recommending that people use beat receivers outside of those auto-generated by Elastic Agent.
Today we require:
receivers:
filebeatreceiver:
filebeat:
inputs:
- data_stream:
dataset: generic
id: filestream-receiver
index: logs-generic-default
paths:
- /var/log/*.log
type: filestream
output:
otelconsumer: {}This can be simplified to the following where a beat receiver without an explicitly configured output implicitly uses the otelconsumer output.
receivers:
filebeatreceiver:
filebeat:
inputs:
- data_stream:
dataset: generic
id: filestream-receiver
index: logs-generic-default
paths:
- /var/log/*.log
type: filestream