Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrating custom AWS Logs package to input package type #10227

Open
ShourieG opened this issue Jun 24, 2024 · 0 comments
Open

Migrating custom AWS Logs package to input package type #10227

ShourieG opened this issue Jun 24, 2024 · 0 comments
Labels
Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team

Comments

@ShourieG
Copy link
Contributor

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.

@ShourieG ShourieG added the Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team label Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team
Projects
None yet
Development

No branches or pull requests

1 participant