opensearch-project / opensearch-project/data-prepper
Add standardization of attributes in data prepper aggregations
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 374
- Forks
- 354
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
Currently, data prepper attributes lists traceId for traces, etc. let's create a standard field which all components can read from, this will help extensibility and in the future if developers want to create custom aggregations they will be able to use plug and play UI components
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered (Optional)
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not identify files, aggregation components, or tests. Start by locating the Data Prepper aggregation implementations and cataloging how attributes such as traceId are represented; done should mean a defined standard field that all components can read and that supports custom aggregations and plug-and-play UI components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100