mayadata-io / mayadata-io/d-operators
use case: ability to monitor an application
Open
Nobody has claimed this yet.
debug
e2e
experiment
monitor
recipe
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
ProblemStatement: As a SRE I want to know the number of failures, errors, successes in last 30 minutes, or last N hours (configurable). I would like to also know the reason behind above failures or errors if any.
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
Begin by reviewing the repository's Go Kubernetes controller structure and declarative patterns. Define how the application-monitoring request fits those patterns, including configurable time windows, failure/error/success counts, and failure reasons; done means those requirements have an agreed implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100