4ef6ea4d10
openstacksdk statsd records for API operations are not response code specific. This change adds a glob to the statsd record path to include all return code response metrics in our API graphs. I believe this change may have come with the openstacksdk 0.103.0 update. We also update paths for servers POST, server details, and flavor details as they have changed. Note the network info is empty which is why we don't get graphs for them, but the paths appear correct. I think this may be beacuse we don't need to query network info in any of our clouds currently. While we are at it we stop updating the airship and inap cloud graphs since those should be cleaned up and this keeps the review overhead smaller. Change-Id: I5a6b80118afaf3b7782a1d1c131787f208583799 |
||
|---|---|---|
| .. | ||
| afs.yaml | ||
| ceph.yaml | ||
| create-nodepool.sh | ||
| datasource.yaml | ||
| git.yaml | ||
| horizon.yaml | ||
| infra-prod-deployment.json | ||
| kolla.yaml | ||
| mosquitto.yaml | ||
| networking-bagpipe.yaml | ||
| networking-bgpvpn.yaml | ||
| networking-odl.yaml | ||
| networking-sfc.yaml | ||
| neutron-dynamic-routing.yaml | ||
| neutron-lib.yaml | ||
| neutron-stable-minusone.yaml | ||
| neutron-stable-minustwo.yaml | ||
| neutron-tempest-plugin.yaml | ||
| neutron-vpnaas.yaml | ||
| neutron.yaml | ||
| nodepool-airship-citycloud.yaml | ||
| nodepool-dib-status.json | ||
| nodepool-inap.yaml | ||
| nodepool-inmotion.yaml | ||
| nodepool-iweb.yaml | ||
| nodepool-limestone.yaml | ||
| nodepool-linaro.yaml | ||
| nodepool-osuosl.yaml | ||
| nodepool-ovh.yaml | ||
| nodepool-rax.yaml | ||
| nodepool-vexxhost.yaml | ||
| nodepool.template | ||
| nodepool.yaml | ||
| octavia.yaml | ||
| openstack-ansible.yaml | ||
| ovsdbapp.yaml | ||
| README.rst | ||
| resource-usage.yaml | ||
| run-grafana.sh | ||
| tap-as-a-service.yaml | ||
| tempest.yaml | ||
| tobiko.yaml | ||
| vmware-nsx.yaml | ||
| zuul-loadbalancer.yaml | ||
| zuul-performance.yaml | ||
| zuul-status.yaml | ||
Developing Graphs
The run-grafana.sh script in this directory will start a
Docker container with Grafana listening on port 3000. It will then load
the datasources and dashboards in this directory. Repeated runs of the
script will re-load the scripts.
You can log into the instance with the username "admin" and password "password". You can then use the Grafana UI to develop graphs.
The "share" icon on the graph in the UI can be used to export a JSON file, which your browser will download. You can copy that to this directory (or update existing files) and submit a review.