Merge pull request #1305 from onflow/vishal/metrika_node_monitoring

adding reference to Metrika node monitoring in the monitoring-nodes page

docs/content/node-operation/monitoring-nodes.mdx

@@ -3,19 +3,19 @@ title: Monitoring Node Health
 sidebar_title: Node Monitoring
 ---
 
-<Callout type="info" title="Logs">
+A Flow node generates logs and publishes metrics as it runs. These logs and metrics can be used to gain insights into the health of the node.
+
+## Logs
 
 Logs are emitted to `stdout` as JSON formed strings. Where these logs are available on your system depends on how you launch your containers. On `systemd` systems for example, the logs will be sent to the system journal daemon `journald`. Other systems may log to `/var/log`.
 
-</Callout>
+## Metrics
 
 Flow nodes produce health metrics in the form of [Prometheus](https://prometheus.io) metrics, exposed from the node software on `/metrics`.
 
 If you wish to make use of these metrics, you'll need to set up a Prometheus server to scrape your Nodes. Alternatively, you can deploy the Prometheus Server on top of your current Flow node to see the metrics without creating an additional server.
 
-<Callout type="info" title="Host Metrics">
-The flow-go application doesn't expose any metrics from the underlying host such as CPU, network, or disk usages. It is recommended you collect these metrics in addition to the ones provided by flow using a tool like node exporter (https://github.com/prometheus/node_exporter)
-</Callout>
+> The flow-go application doesn't expose any metrics from the underlying host such as CPU, network, or disk usages. It is recommended you collect these metrics in addition to the ones provided by flow using a tool like node exporter (https://github.com/prometheus/node_exporter)
 
 1. Copy the following Prometheus configuration into your current flow node
    ```yaml
@@ -46,7 +46,7 @@ The flow-go application doesn't expose any metrics from the underlying host such
 
 4. Open your browser and go to the URL `http://localhost:9090/graph` to load the Prometheus Dashboard
 
-## Key Metric Overview
+### Key Metric Overview
 
 The following are some important metrics produced by the node.
 
@@ -57,3 +57,10 @@ The following are some important metrics produced by the node.
 | consensus_compliance_sealed_height         | Latest height sealed by this node; should increase at a constant rate. |
 | consensus_hotstuff_cur_view                | Current view of the HotStuff consensus algorith; Consensus/Collection only; should increase at a constant rate. |
 | consensus_hotstuff_timeout_seconds         | How long it takes to timeout failed rounds; Consensus/Collection only; values consistently larger than 5s are abnormal. |
+
+
+## Monitoring a Flow node using Metrika Monitoring
+
+Metrika has developed the Flow node monitoring service and is the recommended way of monitoring a Flow node.
+It is a free tool that uses the logs and metrics published by the node and provides access to private node-specific dashboards.
+Follow this [link](https://app.metrika.co/flow/node/install-agent) to setup the Metrika monitoring for your node.