opensearch-project / opensearch-project/data-prepper
Metrics pushing from KCL based on config
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.
Custom cloud watch metrics created by KCL library as part of kinesis source may not be needed for all use cases. In certain use cases, monitoring the lag based on Kinesis metrics is enough. In those cases, KCL related custom metrics pushed to cloud watch becomes costly and unnecessary.
Describe the solution you'd like
Introduce a config to disable/enable pushing metrics to Cloudwatch from Kinesis Source
Describe alternatives you've considered (Optional)
Nil
Additional context
Usecases which are getting migrated from logstash can make use of this.
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
Start by locating the Kinesis source configuration and the KCL metrics setup in the repository. Add a configuration option that controls whether KCL metrics are pushed to CloudWatch, then verify that both enabled and disabled behavior work as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100