Our 'custom packages' currently state that changing the dataset will send the data to a different index. However, these packages create a template such as logs-udp.generic matching logs-udp.generic-* indices. This contradicts the text saying that changing the dataset will send the data to a different index.
Currently, the data itself will go into the new destination, however the initial component template is made to match the incorrect pattern.
In order to resolve this, our custom packages need to be converted to input packages (i.e. type: input)
A separate PR was tracked over sometime to cover the migrations owned by the SSI team, linked here. The ownership of this package lies with the @elastic/obs-ds-hosted-services team, hence creating a separate issue for this. The actual work of migration can be done by either team after necessary discussions.
Our 'custom packages' currently state that changing the dataset will send the data to a different index. However, these packages create a template such as logs-udp.generic matching logs-udp.generic-* indices. This contradicts the text saying that changing the dataset will send the data to a different index.
Currently, the data itself will go into the new destination, however the initial component template is made to match the incorrect pattern.
In order to resolve this, our custom packages need to be converted to input packages (i.e. type: input)
A separate PR was tracked over sometime to cover the migrations owned by the SSI team, linked here. The ownership of this package lies with the @elastic/obs-ds-hosted-services team, hence creating a separate issue for this. The actual work of migration can be done by either team after necessary discussions.