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 convert to input packages (i.e. type: input)

We need to test the user experience when upgrading from a current custom package to the new input package. Are there breaking changes involved and to what extend? Depending on the experience, we may need to discuss deprecation of the current packages and shipping new v2 input packages (but hopefully that can be avoided). Fleet team will need to be engaged to discuss breaking changes. We can also co-ordinate efforts with other teams who own certain inputs.

List of packages to convert:

• CEL
• httpjson (consider depreaction here to avoid confusion over CEL vs httpjon)??
• AWS (S3 and Cloudwatch inputs)
• Azure Blob Storage
• Google Cloud Storage
• Google Pub/Sub
• HTTP Endpoint
• Journald Convert Journald integration to input type #5890
• Kafka Log
• Log
• TCP [tcp] Migrate package to input type #13141
• UDP [udp] Migrate to input package #12385
• Windows [winlog] Convert to an input package. #8010