API v1.1 - Provide more detailed info with /health
Based on the latest discussion, /health should really be called /ping which is for the load balancer. We're going to provide more info with the new /health api.
Some things to report:
* Functional availability (perform create queue, post, list, claim, delete, delete queue)
* Message stats (how many total queues, messages/queue or just total messages, average number of messages/queue, top 10 project by queue size, perhaps by other metrics, everything broken out by storage pool)
* Average request latency (moving load average over 3 different periods - 1 minute, 10 minutes, 30 minutes - TBD)
* Total number of requests per operation - moving average across 3 periods
Blueprint information
- Status:
- Complete
- Approver:
- Kurt Griffiths
- Priority:
- High
- Drafter:
- Feilong Wang
- Direction:
- Approved
- Assignee:
- Feilong Wang
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Feilong Wang
- Completed by
- Feilong Wang
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
feat(v1.1): Implement new /health endpoint for v1.1
Added some ideas for metrics (kgriffs)
Moved to j-3 (kgriffs)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
