[Fleet] OTel input packages should use the receiver dataset by default

[jsoriano]

Input packages use the name of the policy template as default dataset.

In the case of OTel, the default dataset should be the name of the receiver that collects the data. This is the default dataset used with community receivers. Aligning on that will help with content packages, for example the MySQL content package expects documents to contain mysqlreceiver.otel dataset (see here).

To implement this, two things would need to be implemented:

• The dataset entry should be empty for OTel input packages when creating a new policy. And should be optional.
• If left empty, the transform used for routing should not include any dataset, so default is used (this value is set here).

An alternative implementation could be based on using by default the name of the receiver, but this would need to be declared somehow in the package, what would require changes in package-spec and could be more prone to errors.

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[nchaulet]

@jsoriano I started working on this but are we going to have some issue if the dataset is not set? For example for mysqlreceiver it will not create the index template right? I was thinking of permissions issue too but look like we give type-- permissions for all input package.

[jsoriano]

As discussed over slack, this should be indicated by the package as the dataset needs to be known also to create the index template. We could just enforce policy templates to have the expected default dataset in the name, we will to add a test in elastic-package to ensure this.