Skip to content

Commit f16d32d

Browse files
tomkralidisamilan17
authored andcommitted
editorial fix/update (#212)
1 parent 9f08961 commit f16d32d

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

guide/sections/part2/global-services.adoc

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -36,11 +36,10 @@ WIS2 Global Services (Global Brokers, Global Caches, and Global Discovery Catalo
3636

3737
There is no requirement for WIS2 Nodes to provide monitoring metrics. However their WIS2 interfaces may be queried remotely by Global Services, which can then provide metrics on the availability of WIS2 Nodes.
3838

39-
Metrics for WIS2 monitoring should follow the naming convention ``wmo_<program>_<name>``, where ``<program>`` is the name of the responsible WMO programme and ``<name>`` is the name of the metric. Examples of WIS2 metrics include:
39+
Metrics for WIS2 monitoring should follow the naming convention ``wmo_<program>_<name>``, where ``<program>`` is the name of the responsible WMO programme and ``<name>`` is the name of the metric. Examples of WIS2 metrics include (but are not limited to):
4040

41-
``wmo_wis2_gc_downloaded_total``, and
42-
43-
``wmo_wis2_gb_messages_invalid_total``.
41+
* ``wmo_wis2_gc_downloaded_total``
42+
* ``wmo_wis2_gb_messages_invalid_total``
4443

4544
The full set of the WIS2 monitoring metrics is given in WMO: WIS2 Metric Hierarchy footnote:[See https://github.com/wmo-im/wis2-metric-hierarchy.]
4645

0 commit comments

Comments
 (0)