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

Introduce a way to gracefully handle licensing issues from ingest processors #94882

Open
dakrone opened this issue Mar 29, 2023 · 1 comment
Open
Assignees
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement Team:Data Management Meta label for data/management team

Comments

@dakrone
Copy link
Member

dakrone commented Mar 29, 2023

Description

If we eventually have ingest processors that require higher license levels than just "basic", we should also have a way for Fleet to ship those ingest processors.

For example, if we want to ship an integration with a processor with a license level, then we could add a way for documents to skip that processor if they don't have the license level. Optionally, we may want to tag the document in some way to indicate that the processor was present, but did not execute.

@dakrone dakrone added >enhancement :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP labels Mar 29, 2023
@elasticsearchmachine elasticsearchmachine added the Team:Data Management Meta label for data/management team label Mar 29, 2023
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

@dakrone dakrone changed the title Introduce a way to gracefully handle licnesing issues from ingest processors Introduce a way to gracefully handle licensing issues from ingest processors Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement Team:Data Management Meta label for data/management team
Projects
None yet
Development

No branches or pull requests

3 participants