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

Opensearch sink: support ingest pipeline configuration option #3336

Open
sandervandegeijn opened this issue Sep 14, 2023 · 2 comments
Open
Labels
question Further information is requested

Comments

@sandervandegeijn
Copy link

Is your feature request related to a problem? Please describe.
In opensearch you can use ingest pipelines to process data. Fluent-bit, logstash etc support this via a property on the output/sink configuration. Data prepper does not.

Describe the solution you'd like
ingest_pipeline option for the opensearch sink

Describe alternatives you've considered (Optional)
Index templates through dataprepper, but this is overkill imho.

Additional context
N/A

@dlvenable
Copy link
Member

To be sure, you mean using this feature, correct? https://opensearch.org/docs/latest/ingest-pipelines/index/

Also, is there a particular reason you want to use an ingest-pipeline along with Data Prepper? I would generally recommend using Data Prepper instead of ingest-pipelines.

@dlvenable dlvenable added question Further information is requested and removed untriaged labels Oct 24, 2023
@sandervandegeijn
Copy link
Author

Hi, yeah that's the one. Sometimes dataprepper is the choice, but not always. Ingest pipelines an supported and actively developed feature in opensearch which have their uses. i.e. the Elastic log source use ingest pipelines for data manipulation, so we have loaded them into opensearch. Every other log forwarder supports it (logstash plugin, fluent-bit, fluent-d, etc)

This is holding me back from stripping logstash-oss from our egress path from Kafka. Implementation can't be that hard I hope?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Development

No branches or pull requests

2 participants