Adding Metrics / Logging
- Dominant language
- Java
- Stars
- 615
- Forks
- 82
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 7
Description
## What is your idea?
Follow up from https://github.com/aws/event-ruler/pull/18. Added visibility around ruler internals would be helpful when debugging issues or building / updating the code. We want to do this without taking any unnecessary dependency (esp for logging / metrics, where clients can be very opinionated on what they prefer).
## Would you be willing to make the change?
## Additional context
I'll paste relevant github PR discussions as snippets as comments.
Contributor guide
Research direction
Start by reading the discussion in pull request #18 and the relevant issue comments, then inspect the ruler internals to identify what visibility is needed. Define a dependency-free metrics and logging approach; done means the agreed debugging visibility is available without imposing a client logging or metrics dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100