Add API Design for Components Healthcheck
Open
- Dominant language
- No language data
- Stars
- 17
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
As a user, I need some mechanism for checking heartbeat of Components running in my system with Dapr.
Add API Design and the way endpoint, responses etc. will look like for it.
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file, test, or entry point is named. Start by defining the requirements for checking component heartbeats in Dapr, then document the proposed endpoint, request or invocation shape, responses, and completion criteria in the proposal.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100