Skip to content

Built-in Archival and Retrieval process #326

Open
@gitcdb

Description

@gitcdb

Describe the feature

This really does look snazzy, and I'm going to put it through its paces as a POC, but, it'd be nice if we wanted to carve off slices and easily archive them to S3 Glacier with an ability to retrieve and re-insert for comparison sake e.g. we have a rush event every few months. How did the systems perform this month compared to last? What about a year ago?

This might be an edge use case, but we have several yearly rush events based on our clients that happen sporadically throughout the year based on the client, but the big ones are annual events. An ability to use the ingestion pipeline but provide the analytics to compare MoM or YoY for specific events would be quite handy.

Again, this might not be something that you're looking to implement here but I thought I'd ask just in case the use case makes sense.

There's nothing stopping me from devising my own solution to this, but I can't think that I'm alone in wanting to compare activity periods against historical activity periods that go beyond what you'd typically care to store in OpenSearch.

Food for thought perhaps.

Use Case

ease of comparing periods of activity beyond standard OpenSearch storage ranges

Proposed Solution

No response

Other Information

No response

Solution version used

2.3.2

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions