cloudfoundry / cloudfoundry/cloud_controller_ng
More direct access to processes states
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 207
- Forks
- 373
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 56
Description
Context
Creation of a centralised monitoring dashboard of apps based on the api (list of crashed apps).
Issue
With the current existing endpoints, getting "real" state for a list of apps requires too many network calls.
As far as I know, the only way to know if an app is crashed is to call the stats endpoints which requires one call per process /v3/processes/process-id/stats.
Current result
When getting an app, the received object only contains the desired state of the app (STARTED, STOPPED). This desired
state does not reflect the "real" state of the app processes (we might be crashed).
Possible Fix
A few ideas :
- Provide an endpoint to get all the stats for all process :
v3/stats - Include the "real" state (processes states) in the app response.
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
The issue names the app endpoints and the per-process /v3/processes/process-id/stats endpoint; start by reviewing how those entry points expose desired and real process state. Decide between an aggregate stats endpoint and adding process state to app responses, then verify that a list of apps can be checked without one stats request per process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100