forked from docs/docsportal
fixing small issues and references
This commit is contained in:
parent
e81cf6db24
commit
e222d6daf8
@ -2,7 +2,6 @@
|
|||||||
What Are The Annotations?
|
What Are The Annotations?
|
||||||
#########################
|
#########################
|
||||||
|
|
||||||
|
|
||||||
Annotations provide a way to mark points on the graph with rich events. When you
|
Annotations provide a way to mark points on the graph with rich events. When you
|
||||||
hover over an annotation you can get event description and event tags. The text
|
hover over an annotation you can get event description and event tags. The text
|
||||||
field can include links to other systems with more detail.
|
field can include links to other systems with more detail.
|
||||||
|
@ -5,7 +5,6 @@ Logs
|
|||||||
====
|
====
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
- Every single job run log is stored on OpenStack Swift object storage.
|
- Every single job run log is stored on OpenStack Swift object storage.
|
||||||
- Each single job log file provides unique URL which can be accessed to see log
|
- Each single job log file provides unique URL which can be accessed to see log
|
||||||
details
|
details
|
||||||
|
@ -43,7 +43,7 @@ New Test Scenario introduction
|
|||||||
==============================
|
==============================
|
||||||
|
|
||||||
As already mentioned playbook scenarios are stored in separate repository on
|
As already mentioned playbook scenarios are stored in separate repository on
|
||||||
`github <https://github.com/opentelekomcloud-infra/apimon-test>`_. Due to the
|
`Github <https://github.com/opentelekomcloud-infra/apimon-tests>`_. Due to the
|
||||||
fact that we have various environments which differ between each other by
|
fact that we have various environments which differ between each other by
|
||||||
location, supported services, different flavors, etc it's required to have
|
location, supported services, different flavors, etc it's required to have
|
||||||
monitoring configuration matrix which defines the monitoring standard and scope
|
monitoring configuration matrix which defines the monitoring standard and scope
|
||||||
@ -126,8 +126,10 @@ be complicated to transfer processing logic of metrics on grafana. Therefore
|
|||||||
tags feature on task level introduces possibility to address custom metrics.
|
tags feature on task level introduces possibility to address custom metrics.
|
||||||
|
|
||||||
|
|
||||||
In following example the custom metric stores the result of multiple tasks in
|
In following example (snippet from `scenario2_simple_ece.yaml
|
||||||
special metric name create_server::
|
<https://github.com/opentelekomcloud-infra/apimon-tests/blob/master/playbooks/scenario2_simple_ecs.yaml>`_)
|
||||||
|
custom metric stores the result of multiple tasks in special metric name
|
||||||
|
create_server::
|
||||||
|
|
||||||
- name: Create Server in default AZ
|
- name: Create Server in default AZ
|
||||||
openstack.cloud.server:
|
openstack.cloud.server:
|
||||||
|
Loading…
x
Reference in New Issue
Block a user