Added missing links to Grafana dashboards

Author: anton-bobkov

ydb/docs/en/core/dev/troubleshooting/performance/hardware/_includes/io-bandwidth.md

@@ -1,4 +1,4 @@
-1. Open the **Distributed Storage Overview** dashboard in Grafana.
+1. Open the **[Distributed Storage Overview](../../../../../reference/observability/metrics/grafana-dashboards.md)** dashboard in Grafana.
 
 1. On the **DiskTimeAvailable and total Cost relation** chart, see if the **Total Cost** spikes cross the **DiskTimeAvailable** level.
 

ydb/docs/en/core/dev/troubleshooting/performance/hardware/disk-space.md

@@ -4,7 +4,7 @@ A lack of available disk space can prevent the database from storing new data, r
 
 ## Diagnostics
 
-1. See if the **DB overview > Storage** charts in Grafana show any spikes.
+1. See if the **[DB overview > Storage](../../../../reference/observability/metrics/grafana-dashboards.md#dboverview)** charts in Grafana show any spikes.
 
 1. In [Embedded UI](../../../../reference/embedded-ui/index.md), on the **Storage** tab, analyze the list of available storage groups and nodes and their disk usage.
 

ydb/docs/en/core/dev/troubleshooting/performance/hardware/insufficient-memory.md

@@ -34,11 +34,11 @@ Additionally, which components within the  {{ ydb-short-name }} process consume
 
 1. Determine whether memory usage reached 100% of capacity.
 
-    1. Open the **DB overview** dashboard in Grafana.
+    1. Open the **[DB overview](../../../../reference/observability/metrics/grafana-dashboards.md#dboverview)** dashboard in Grafana.
 
     1. Analyze the charts in the **Memory** section.
 
-1. Determine whether the user load on {{ ydb-short-name }} has increased. Analyze the following charts on the **DB overview** dashboard in Grafana:
+1. Determine whether the user load on {{ ydb-short-name }} has increased. Analyze the following charts on the **[DB overview](../../../../reference/observability/metrics/grafana-dashboards.md#dboverview)** dashboard in Grafana:
 
     - **Requests** chart
     - **Request size** chart

ydb/docs/en/core/dev/troubleshooting/performance/queries/_includes/overloaded-errors.md

@@ -18,6 +18,6 @@
 
 1. To check if the spikes in overloaded errors were caused by tablet splits and merges, see [{#T}](../../schemas/splits-merges.md).
 
-1. To check if the spikes in overloaded errors were caused by exceeding the 1000 limit of open sessions, in the Grafana **DB status** dashboard, see the **Session count by host** chart.
+1. To check if the spikes in overloaded errors were caused by exceeding the 1000 limit of open sessions, in the Grafana **[DB status](../../../../../reference/observability/metrics/grafana-dashboards.md#dbstatus)** dashboard, see the **Session count by host** chart.
 
 1. See the [overloaded shards](../../schemas/overloaded-shards.md) issue.

ydb/docs/en/core/dev/troubleshooting/performance/schemas/_includes/splits-merges.md

@@ -1,4 +1,4 @@
-1. See if the **Split / Merge partitions** chart in the **DB status** Grafana dashboard shows any spikes.
+1. See if the **Split / Merge partitions** chart in the **[DB status](../../../../../reference/observability/metrics/grafana-dashboards.md#dbstatus)** Grafana dashboard shows any spikes.
 
     ![](../_assets/splits-merges.png)