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

Feature Request: View/Dump All Metadata Associated with OpenSearch Records #5338

Open
neethu00 opened this issue Jan 16, 2025 · 2 comments
Open
Labels
follow up question Further information is requested

Comments

@neethu00
Copy link

neethu00 commented Jan 16, 2025

Is your feature request related to a problem? Please describe.
In OpenSearch. Currently, users have to explicitly know or keep track of any metadata to use it when working with records in OpenSearch. This makes it difficult to access and utilize important information about how records were sourced, processed, and sinked to OpenSearch.

Describe the solution you'd like
Implement a feature that allows users to easily view or dump all metadata associated with a record in OpenSearch. This should include information about how the record was sourced, processed, and sinked to OpenSearch. The solution should provide a simple and intuitive way to access this metadata without requiring users to manually track or remember specific metadata fields.

Additional context

This feature would greatly improve the traceability and auditability of data in OpenSearch. It would be particularly useful for debugging, data lineage tracking, and ensuring compliance with data governance policies. The ability to easily access and view all metadata associated with a record would enhance the overall usability and value of the OpenSearch system for data management and analysis tasks.

@dlvenable
Copy link
Member

@neethu00 , Thank you for opening this issue.

We are looking for some clarity on the ask here. Are you wanting this to help debug Data Prepper pipelines? Or this more to have a full audit history of events?

Do you want this metadata to be stored in OpenSearch? Or do you want them in the logs?

Can you elaborate on what metadata you are looking to include?

@dlvenable dlvenable added question Further information is requested follow up and removed untriaged labels Jan 21, 2025
@neethu00
Copy link
Author

@dlvenable
Please find the customer expection below:

The expectation is that I can output the logEvents field AND be able to identify the source SubscriptionFilter through the subscriptionFilters key to include in the record i'm outputting to OpenSearch. Is this possible

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

No branches or pull requests

2 participants