opensearch-project / opensearch-project/data-prepper
Automated testing for /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.
Create automated tests to verify Prometheus and CloudWatch metrics are available at /metrics/prometheus and /metrics/sys if configured.
Describe the solution you'd like
Add an automated e2e test to verify.
Describe alternatives you've considered (Optional)
- enhance existing e2e test - less focused test
- create a smoke test - not really the place to catch bugs
Additional context
A bug where configured metrics are not available was discovered in main by @graytaylor0
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 existing end-to-end test setup and the code or configuration exposing /metrics/prometheus and /metrics/sys. Add focused coverage for configured Prometheus and CloudWatch metrics, then run the relevant e2e test command and confirm both endpoints are verified when enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java, prometheus
- Domain
- observability, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100