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

Evaluate the use of ES DataStreams instead of Index #112

Open
ricsanfre opened this issue Mar 11, 2023 · 0 comments
Open

Evaluate the use of ES DataStreams instead of Index #112

ricsanfre opened this issue Mar 11, 2023 · 0 comments
Labels
analysis Analysis is required

Comments

@ricsanfre
Copy link
Owner

Enhancement Request

Since Elasticsearch 7.9, Data Streams concept was introduced.

A data stream lets you store append-only time series data across multiple indices while giving you a single named resource for requests. Data streams are well-suited for logs, events, metrics, and other continuously generated data.
You can use index lifecycle management (ILM) to automate the management of these backing indices. For example, you can use ILM to automatically move older backing indices to less expensive hardware and delete unneeded indices. ILM can help you reduce costs and overhead as your data grows.

Use this new concept to automatically configure retention policies of the data using ILM policies.

References

Implementation Details

Fluend elastic-search-plugin already support DataStreams: https://github.com/uken/fluent-plugin-elasticsearch#configuration---elasticsearch-output-data-stream

@ricsanfre ricsanfre changed the title Analyze the use of ES DataStreams instead of Index Evaluate the use of ES DataStreams instead of Index Mar 11, 2023
@ricsanfre ricsanfre added the analysis Analysis is required label Mar 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analysis Analysis is required
Projects
None yet
Development

No branches or pull requests

1 participant