public/grafana
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[v8.2.x] Docs: updated broken links (#74933)

Browse Source 
[v8.5.x] Docs: updated broken links (#74880)

Updated broken links

(cherry picked from commit 00dce5d11d)

Co-authored-by: Isabel <76437239+imatwawana@users.noreply.github.com>
This commit is contained in:
Grot (@grafanabot)
2023-09-18 10:10:53 -05:00
committed by GitHub
co-authored by Isabel
parent 5e5e6f399c
commit ea399f4391
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/whatsnew/whats-new-in-v5-0.md
+3 -3
View File
@@ -105,7 +105,7 @@ and alerts as well.
### Data sources
Data sources can now be set up using config files. These data sources are by default not editable from the Grafana GUI.
It's also possible to update and delete data sources from the config file. More info in the [data source provisioning docs](/administration/provisioning/#datasources).
It's also possible to update and delete data sources from the config file. More info in the [data source provisioning docs]({{< relref "../administration/provisioning#data-sources" >}}).
### Dashboards
@@ -113,7 +113,7 @@ We also deprecated the `[dashboard.json]` in favor of our new dashboard provisio
in sync with dashboards in Grafana's database. The dashboard provisioner has multiple advantages over the old
`[dashboard.json]` feature. Instead of storing the dashboard in memory we now insert the dashboard into the database,
which makes it possible to star them, use one as the home dashboard, set permissions and other features in Grafana that
expects the dashboards to exist in the database. More info in the [dashboard provisioning docs]({{< relref "../administration/provisioning.md" >}})
expects the dashboards to exist in the database. More info in the [dashboard provisioning docs]({{< relref "../administration/provisioning#dashboards" >}})
## Graphite Tags and Integrated Function Docs
@@ -132,7 +132,7 @@ We are introducing a new unique identifier (`uid`) in the dashboard JSON model.
generated if not provided when creating a dashboard and will have a length of 9-12 characters.
The unique identifier allows having persistent URLs for accessing dashboards, sharing them
between instances and when using [dashboard provisioning](<(/administration/provisioning/#reusable-dashboard-urls)>). This means that dashboard can
between instances and when using [dashboard provisioning]({{< relref "../administration/provisioning#reusable-dashboard-urls" >}}). This means that dashboard can
be renamed without breaking any links. We're changing the URL format for dashboards
from `/dashboard/db/:slug` to `/d/:uid/:slug`. We'll keep supporting the old slug-based URLs for dashboards
and redirects to the new one for backward compatibility. Please note that the old slug-based URLs