summaryrefslogtreecommitdiff
path: root/doc/operations/metrics/dashboards/panel_types.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/operations/metrics/dashboards/panel_types.md')
-rw-r--r--doc/operations/metrics/dashboards/panel_types.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/operations/metrics/dashboards/panel_types.md b/doc/operations/metrics/dashboards/panel_types.md
index fd9d2bf7899..86f6776e273 100644
--- a/doc/operations/metrics/dashboards/panel_types.md
+++ b/doc/operations/metrics/dashboards/panel_types.md
@@ -1,7 +1,7 @@
---
stage: Monitor
group: Health
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
---
# Panel types for dashboards **(CORE)**
@@ -39,7 +39,7 @@ Note the following properties:
![area panel chart](img/prometheus_dashboard_area_panel_type_v12_8.png)
-Starting in [version 12.8](https://gitlab.com/gitlab-org/gitlab/-/issues/202696), the y-axis values will automatically scale according to the data. Previously, it always started from 0.
+Starting in [version 12.8](https://gitlab.com/gitlab-org/gitlab/-/issues/202696), the y-axis values scale according to the data. Previously, it always started from 0.
## Anomaly chart
@@ -229,7 +229,7 @@ For example, if you have a query value of `53.6`, adding `%` as the unit results
## Gauge
-CAUTION: **Warning:**
+WARNING:
This panel type is an _alpha_ feature, and is subject to change at any time
without prior notice!
@@ -307,7 +307,7 @@ Note the following properties:
![heatmap panel type](img/heatmap_panel_type.png)
-CAUTION: **Warning:**
+WARNING:
When a query returns too many data points, the heatmap data bucket dimensions tend downwards to 0, making the chart's data invisible, as shown in the image below. To fix this problem, limit the amount of data returned by changing the time range filter on the metrics dashboard UI, or adding the **step** property to your dashboard's YAML file.
![heatmap chart_too_much_data](img/heatmap_chart_too_much_data_v_13_2.png)