Fix link format in COMAC monitoring doc
Change-Id: I4d27da31ca2e008775940db59dd966a28d643aa8
diff --git a/profiles/comac/configure/monitoring.md b/profiles/comac/configure/monitoring.md
index 21c9b5f..54c08b7 100644
--- a/profiles/comac/configure/monitoring.md
+++ b/profiles/comac/configure/monitoring.md
@@ -6,7 +6,7 @@
## Grafana-via-Prometheus for COMAC monitoring
-In COMAC, we are using `nem-monitoring` chart for monitoring. The chart is part of the `cord-platform` helm-chart, but if you need to install it, please refer to [this guide] (https://guide.opencord.org/charts/logging-monitoring.html#nem-monitoring-charts).
+In COMAC, we are using `nem-monitoring` chart for monitoring. The chart is part of the `cord-platform` helm-chart, but if you need to install it, please refer to [this guide](https://guide.opencord.org/charts/logging-monitoring.html#nem-monitoring-charts).
`nem-monitoring` includes Grafana, Prometheus, and metrics exporters. The chart is capable for monitoring and visualization in single cluster by default. However, if you want to deploy COMAC on multi-cluster, the monitoring system should pull metrics from multi-cluster.
@@ -14,9 +14,9 @@
It depends on exporters which metrics are exposed. The exposed metrics are collected and stored in Prometheus then the metrics can be used by Grafana to create dashboards. In COMAC environment, we basically deploy 3 exporters as follows.
-- [cAdvisor] (https://github.com/google/cadvisor)
-- [Kube-state-metrics] (https://github.com/kubernetes/kube-state-metrics)
-- [Node-exporter] (https://github.com/prometheus/node_exporter)
+- [cAdvisor](https://github.com/google/cadvisor)
+- [Kube-state-metrics](https://github.com/kubernetes/kube-state-metrics)
+- [Node-exporter](https://github.com/prometheus/node_exporter)
They expose resource usage and performance characteristics of running containers, metrics about Kubernetes objects, and hardware/OS metrics. Basically, the monitoring system including Grafana, Prometheus, and metrics exporters in the edge cluster. Thus, we should deploy exporters in the central cluster and make the monitoring system interacts with them as following figure.