opensearch-project / opensearch-project/data-prepper
S3 DLQ Writer response code metrics
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.
Adding metrics based on the response code for the S3 PutObject call would be useful. This would give easier insight into the types of failures the DLQ Writer is experiencing.
Describe the solution you'd like
Metrics for:
- Auth issues
- Access Denied
- Bad Request
- TImeout
Describe alternatives you've considered (Optional)
There are a lot of exceptions that can be thrown. Are there any we should prioritize over the three that are listed?
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 S3 DLQ Writer and its S3 PutObject call, then inspect how existing metrics and exceptions are handled. Define the response-code categories to report, including the listed authentication, access-denied, bad-request, and timeout cases, and verify that the resulting metrics expose the writer's failure types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100