openstack/neutron
Code Issues Proposed changes

Doc: Due to recent grafana upgrade change urls in doc

Browse Source 
grafana urls contain uuid, include that to links.

Change-Id: Ib4810d746c94e05ea75c44fa828b097a88985fe7
This commit is contained in:
elajkat 2022-02-09 10:44:19 +01:00
parent f324ddf769
commit 129760b84f
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/contributor/dashboards/index.rst
View File

@ -20,9 +20,9 @@ Grafana Dashboards
Look for neutron and networking-* dashboard by names by going to the following link: Look for neutron and networking-* dashboard by names by going to the following link:
`Grafana <http://grafana.openstack.org/>`_ `Grafana <https://grafana.opendev.org/>`_
For instance: For instance:
* `Neutron <http://grafana.openstack.org/dashboard/db/neutron-failure-rate>`_ * `Neutron <https://grafana.opendev.org/d/f913631585/neutron-failure-rate>`_
* `Neutron-lib <http://grafana.openstack.org/dashboard/db/neutron-lib-failure-rate>`_ * `Neutron-lib <https://grafana.opendev.org/d/92ab2dc01e/neutron-lib-failure-rate>`_

2
doc/source/contributor/policies/gate-failure-triage.rst
View File

@ -8,7 +8,7 @@ Spotting Gate Failures
---------------------- ----------------------
This can be achieved using several tools: This can be achieved using several tools:
* `Grafana dashboard <http://grafana.openstack.org/dashboard/db/neutron-failure-rate>`_ * `Grafana dashboard <https://grafana.opendev.org/d/f913631585/neutron-failure-rate>`_
* `logstash <http://logstash.openstack.org/>`_ * `logstash <http://logstash.openstack.org/>`_
For checking gate failures with logstash the following query will return failures for a specific job: For checking gate failures with logstash the following query will return failures for a specific job:

2
doc/source/contributor/policies/gerrit-recheck.rst
View File

@ -15,7 +15,7 @@ example unable to fetch things from external resources like git or pip due to
outage. Such failures outside of OpenStack world are not worth tracking in outage. Such failures outside of OpenStack world are not worth tracking in
launchpad and you can recheck leaving couple of words what went wrong. Data launchpad and you can recheck leaving couple of words what went wrong. Data
about gate stability is collected and visualized via about gate stability is collected and visualized via
`Grafana <http://grafana.openstack.org/dashboard/db/neutron-failure-rate>`_. `Grafana <https://grafana.opendev.org/d/f913631585/neutron-failure-rate>`_.
Please, do not recheck without providing the bug number for the failed job. Please, do not recheck without providing the bug number for the failed job.
For example, do not just put an empty "recheck" comment but find the related For example, do not just put an empty "recheck" comment but find the related

2
doc/source/contributor/stadium/governance.rst
View File

@ -84,7 +84,7 @@ mature OpenStack projects:
documentations available. documentations available.
* Exhaustive OpenStack CI coverage: unit, functional, and tempest coverage * Exhaustive OpenStack CI coverage: unit, functional, and tempest coverage
using OpenStack CI (upstream) resources so that `Grafana <http://grafana.openstack.org/dashboard/db/neutron-failure-rate>`_ using OpenStack CI (upstream) resources so that `Grafana <https://grafana.opendev.org/d/f913631585/neutron-failure-rate>`_
and `OpenStack Health <http://status.openstack.org/openstack-health/#/>`_ and `OpenStack Health <http://status.openstack.org/openstack-health/#/>`_
support is available. Access to CI resources and historical data by the support is available. Access to CI resources and historical data by the
team is key to ensuring stability and robustness of a project. team is key to ensuring stability and robustness of a project.