diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-11-01 09:10:48 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-11-01 09:10:48 +0000 |
| commit | 58c42f2f454c5223062b08a47c5add4e52ad677f (patch) | |
| tree | d85ab2e038c962124675b28c221a7481c7d04901 /doc/administration/monitoring/performance | |
| parent | 38a40989000eb88315dca94e72a8341c15d034db (diff) | |
| download | gitlab-ce-58c42f2f454c5223062b08a47c5add4e52ad677f.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/monitoring/performance')
| -rw-r--r-- | doc/administration/monitoring/performance/grafana_configuration.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/administration/monitoring/performance/grafana_configuration.md b/doc/administration/monitoring/performance/grafana_configuration.md index 49f92572cc5..92e9672cdb6 100644 --- a/doc/administration/monitoring/performance/grafana_configuration.md +++ b/doc/administration/monitoring/performance/grafana_configuration.md @@ -133,8 +133,8 @@ However, you should **not** reinstate your old data _except_ under one of the fo If you require access to your old Grafana data but don't meet one of these criteria, you may consider: 1. Reinstating it temporarily. -1. [Exporting the dashboards](https://grafana.com/docs/grafana/latest/dashboards/export-import/#exporting-a-dashboard) you need. -1. Refreshing the data and [re-importing your dashboards](https://grafana.com/docs/grafana/latest/dashboards/export-import/#import-dashboard). +1. [Exporting the dashboards](https://grafana.com/docs/grafana/latest/dashboards/manage-dashboards/#export-and-import-dashboards) you need. +1. Refreshing the data and [re-importing your dashboards](https://grafana.com/docs/grafana/latest/dashboards/manage-dashboards/#export-and-import-dashboards). WARNING: These actions pose a temporary vulnerability while your old Grafana data is in use. |