feat(v1.1): Implement new /health endpoint for v1.1

Bug #1360537 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Invalid
Undecided
Unassigned

Bug Description

https://review.openstack.org/76555

Dear documentation bug triager. This bug was created here because we did not know how to map the project name "openstack/zaqar" to a launchpad project name. This indicates that the notify_impact config needs tweaks. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 13df51be82fcac8cdb0e8d4e77824a5ddb81fea7
Author: Fei Long Wang <email address hidden>
Date: Tue Feb 18 09:28:51 2014 +0800

    feat(v1.1): Implement new /health endpoint for v1.1

    The new /health endpoint of v1.1 is different from the /health
    of v1.0. In v1.1 /health endpoint we will return a set of KPI
    (Key Performance Indicator) of the target Marconi server. The
    API response will be like below:

    {
        "mongo_pool_1": {
            "message_volume": {
                "claimed": 0,
                "total": 0,
                "free": 0
            },
            "storage_reachable": true,
            "operation_status": {
                "create_queue": {
                    "seconds": 0.0021300315856933594,
                    "ref": null,
                    "succeeded": true
                },
                "post_messages": {
                    "seconds": 0.033502817153930664,
                    "ref": null,
                    "succeeded": true
                },
                "list_messages": {
                    "seconds": 0.000013113021850585938,
                    "ref": null,
                    "succeeded": true
                },
                "claim_messages": {
                    "seconds": 0.0013759136199951172,
                    "ref": "3f515f37-58a0-4c81-8214-3e92979b82e7",
                    "succeeded": false
                },
                "delete_queue": {
                    "seconds": 0.0030739307403564453,
                    "ref": null,
                    "succeeded": true
                }
            }
        },
        "mongo_pool_2": {
            "message_volume": {
                "claimed": 0,
                "total": 0,
                "free": 0
            },
            "storage_reachable": true,
            "operation_status": {
                "create_queue": {
                    "seconds": 0.0011799335479736328,
                    "ref": null,
                    "succeeded": true
                },
                "post_messages": {
                    "seconds": 0.024316072463989258,
                    "ref": null,
                    "succeeded": true
                },
                "list_messages": {
                    "seconds": 0.000008106231689453125,
                    "ref": null,
                    "succeeded": true
                },
                "claim_messages": {
                    "seconds": 0.000576019287109375,
                    "ref": "68629fda-b4ce-4cf9-978a-df0df8df36a7",
                    "succeeded": false
                },
                "delete_queue": {
                    "seconds": 0.003300905227661133,
                    "ref": null,
                    "succeeded": true
                }
            }
        },
        "catalog_reachable": true
    }

    docImpact
    Implements: blueprint detailed-health

    Change-Id: I6b281132e2fef8ce65ce54b9d6be297571f8b170

Tags: zaqar
Revision history for this message
Andreas Jaeger (jaegerandi) wrote :

zaqar is not documented currently.

Changed in openstack-manuals:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.