Merge branch 'docs-aqualls-redo-dashboards-page' into 'master'

Begin revising the dashboards page

See merge request gitlab-org/gitlab!37242

app/views/projects/blob/viewers/_metrics_dashboard_yml.html.haml

@@ -8,4 +8,4 @@
     - viewer.errors.messages.each do |error|
       %li= error.join(': ')
 
-= link_to _('Learn more'), help_page_path('operations/metrics/dashboards/index.md', anchor: 'defining-custom-dashboards-per-project')
+= link_to _('Learn more'), help_page_path('operations/metrics/dashboards/index.md')

doc/administration/monitoring/gitlab_self_monitoring_project/index.md

@@ -58,7 +58,7 @@ The dashboard uses metrics available in
 ![GitLab self monitoring default dashboard](img/self_monitoring_default_dashboard.png)
 
 You can also
-[create your own dashboards](../../../operations/metrics/dashboards/index.md#defining-custom-dashboards-per-project).
+[create your own dashboards](../../../operations/metrics/dashboards/index.md).
 
 ## Connection to Prometheus
 
@@ -83,8 +83,8 @@ Once the webhook is setup, you can
 
 You can add custom metrics in the self monitoring project by:
 
-1. [Duplicating](../../../operations/metrics/dashboards/index.md#duplicating-a-gitlab-defined-dashboard) the default dashboard.
-1. [Editing](../../../operations/metrics/dashboards/index.md#view-and-edit-the-source-file-of-a-custom-dashboard) the newly created dashboard file and configuring it with [dashboard YAML properties](../../../operations/metrics/dashboards/yaml.md).
+1. [Duplicating](../../../operations/metrics/dashboards/index.md#duplicate-a-gitlab-defined-dashboard) the default dashboard.
+1. [Editing](../../../operations/metrics/index.md) the newly created dashboard file and configuring it with [dashboard YAML properties](../../../operations/metrics/dashboards/yaml.md).
 
 ## Troubleshooting
 

doc/operations/metrics/embed.md

@@ -53,7 +53,7 @@ Metric charts may also be hidden:
 ![Show Hide](../../user/project/integrations/img/hide_embedded_metrics_v12_10.png)
 
 You can open the link directly into your browser for a
-[detailed view of the data](dashboards/index.md#expand-panel).
+[detailed view of the data](dashboards/index.md#chart-context-menu).
 
 ## Embedding metrics in issue templates
 

doc/operations/metrics/index.md

@@ -41,8 +41,11 @@ navigation bar contains:
   Starred dashboards display a solid star **{star}** button, and display first
   in the **Dashboard** dropdown list.
   ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/214582) in GitLab 13.0.)
+- **Edit dashboard** - Edit the source YAML file of a custom dashboard. Only available on
+  [custom dashboards](dashboards/index.md).
+  ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/34779) in GitLab 12.5.)
 - **Create dashboard** **{file-addition-solid}** - Create a
-  [new custom dashboard for your project](dashboards/index.md#adding-a-new-dashboard-to-your-project).
+  [new custom dashboard for your project](dashboards/index.md#add-a-new-dashboard-to-your-project).
 - **Metrics settings** **{settings}** - Configure the
   [settings for this dashboard](dashboards/index.md#manage-the-metrics-dashboard-settings).
 

doc/user/incident_management/index.md

@@ -105,11 +105,8 @@ in incidents and issue templates.
 
 You can view more details about an embedded metrics panel from the context menu.
 To access the context menu, click the **{ellipsis_v}** **More actions** dropdown box
-above the upper right corner of the panel. The options are:
-
-- [View logs](#view-logs-from-metrics-panel).
-- **Download CSV** - Data from embedded charts can be
-  [downloaded as CSV](../../operations/metrics/dashboards/index.md#downloading-data-as-csv).
+above the upper right corner of the panel. For a list of options, see
+[Chart context menu](../../operations/metrics/dashboards/index.md#chart-context-menu).
 
 #### View logs from metrics panel
 
@@ -117,7 +114,7 @@ above the upper right corner of the panel. The options are:
 > - [Moved](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/25455) to [GitLab Core](https://about.gitlab.com/pricing/) 12.9.
 
 Viewing logs from a metrics panel can be useful if you're triaging an application
-incident and need to [explore logs](../../operations/metrics/dashboards/index.md#view-logs-ultimate)
+incident and need to [explore logs](../../operations/metrics/dashboards/index.md#chart-context-menu)
 from across your application. These logs help you understand what is affecting
 your application's performance and resolve any problems.
 

doc/user/project/integrations/prometheus.md

@@ -121,7 +121,8 @@ one of them will be used:
   [Prometheus manual configuration](#manual-configuration-of-prometheus)
   and a [managed Prometheus on Kubernetes](#managed-prometheus-on-kubernetes),
   the manual configuration takes precedence and is used to run queries from
-  [dashboards](../../../operations/metrics/dashboards/index.md#defining-custom-dashboards-per-project) and [custom metrics](../../../operations/metrics/index.md#adding-custom-metrics).
+  [custom dashboards](../../../operations/metrics/dashboards/index.md) and
+  [custom metrics](../../../operations/metrics/index.md#adding-custom-metrics).
 - If you have managed Prometheus applications installed on Kubernetes clusters
   at **different** levels (project, group, instance), the order of precedence is described in
   [Cluster precedence](../../instance/clusters/index.md#cluster-precedence).