[v11.5] Remove relref shortcodes (#101707)
* manually replce all shared relrefs * relref replace - grafana v11.5 * Merge branch 'master' into robbymilo/relref-replace-grafana-11.5 * manual fixes * replace ref shortcodes * Merge branch 'master' into robbymilo/relref-replace-grafana-11.5 * update readme * update test --------- Co-authored-by: Jack Baldry <jack.baldry@grafana.com>
This commit is contained in:
Robby Milo
co-authored by
Jack Baldry
Jack Baldry
parent
fe4442a7fb
commit
96d15d9091
@@ -22,7 +22,7 @@ We recommend that you upgrade Grafana often to stay current with the latest fixe
|
||||
|
||||
Because Grafana upgrades are backward compatible, the upgrade process is straightforward, and dashboards and graphs will not change.
|
||||
|
||||
To learn what's available in a Grafana release, refer to [What's New]({{< relref "../whatsnew" >}}).
|
||||
To learn what's available in a Grafana release, refer to [What's New](../whatsnew/).
|
||||
|
||||
Refer to any of the following upgrade guides:
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ This section describes technical changes associated with this release of Grafana
|
||||
|
||||
### Plugins
|
||||
|
||||
Grafana now requires all plugins to be signed. If a plugin is not signed Grafana will not load/start it. This is an additional security measure to make sure plugin files and binaries haven't been tampered with. All Grafana Labs authored plugins, including Enterprise plugins, are now signed. It's possible to allow unsigned plugins using a configuration setting, but is something we strongly advise against doing. For more information about this setting, refer to [allow loading unsigned plugins]({{< relref "../../setup-grafana/configure-grafana#allow_loading_unsigned_plugins" >}}).
|
||||
Grafana now requires all plugins to be signed. If a plugin is not signed Grafana will not load/start it. This is an additional security measure to make sure plugin files and binaries haven't been tampered with. All Grafana Labs authored plugins, including Enterprise plugins, are now signed. It's possible to allow unsigned plugins using a configuration setting, but is something we strongly advise against doing. For more information about this setting, refer to [allow loading unsigned plugins](../../setup-grafana/configure-grafana/#allow_loading_unsigned_plugins).
|
||||
|
||||
### Grafana Live
|
||||
|
||||
@@ -38,7 +38,7 @@ When WebSocket connection is established, Grafana checks the request Origin head
|
||||
|
||||
To handle many concurrent WebSocket connections you may need to tune your OS settings or infrastructure. Grafana Live is enabled by default and supports 100 concurrent WebSocket connections max to avoid possible problems with the file descriptor OS limit. As soon as your setup meets the requirements to scale the number of persistent connections this limit can be increased. You also have an option to disable Grafana Live.
|
||||
|
||||
Refer to [Grafana Live configuration]({{< relref "../../setup-grafana/set-up-grafana-live" >}}) documentation for more information.
|
||||
Refer to [Grafana Live configuration](../../setup-grafana/set-up-grafana-live/) documentation for more information.
|
||||
|
||||
### Postgres, MySQL, Microsoft SQL Server data sources
|
||||
|
||||
@@ -65,6 +65,6 @@ ORDER BY time
|
||||
There are two possible workarounds to resolve this problem:
|
||||
|
||||
1. In Grafana v8.0.3, use an alias of the string column selected as `metric`. for example, `hostname as metric`.
|
||||
2. Use the [Standard field definitions' display name]({{< relref "../../panels-visualizations/configure-standard-options#display-name" >}}) to format the alias. For the preceding example query, you would use `${__field.labels.hostname}` option.
|
||||
2. Use the [Standard field definitions' display name](../../panels-visualizations/configure-standard-options/#display-name) to format the alias. For the preceding example query, you would use `${__field.labels.hostname}` option.
|
||||
|
||||
For more information, refer to the our relational databases documentation of [Postgres]({{< relref "../../datasources/postgres#time-series-queries" >}}), [MySQL]({{< relref "../../datasources/mysql#time-series-queries" >}}), [Microsoft SQL Server]({{< relref "../../datasources/mssql/query-editor#time-series-query-examples" >}}).
|
||||
For more information, refer to the our relational databases documentation of [Postgres](../../datasources/postgres/#time-series-queries), [MySQL](../../datasources/mysql/#time-series-queries), [Microsoft SQL Server](../../datasources/mssql/query-editor/#time-series-query-examples).
|
||||
|
||||
@@ -34,4 +34,4 @@ As of Grafana v8.1, we no longer support unencrypted storage of passwords and ba
|
||||
Since Grafana v6.2, new or updated data sources store passwords and basic auth passwords encrypted. However, unencrypted passwords and basic auth passwords were also allowed.
|
||||
{{% /admonition %}}
|
||||
|
||||
To migrate to encrypted storage, use a `grafana-cli` command to migrate all of your data sources to use encrypted storage of secrets. See [migrate data and encrypt passwords]({{< relref "../../cli#migrate-data-and-encrypt-passwords" >}}) for further instructions.
|
||||
To migrate to encrypted storage, use a `grafana-cli` command to migrate all of your data sources to use encrypted storage of secrets. See [migrate data and encrypt passwords](../../cli/#migrate-data-and-encrypt-passwords) for further instructions.
|
||||
|
||||
@@ -59,7 +59,7 @@ In the Prometheus data source, when grafana receives numeric data from Prometheu
|
||||
|
||||
<!-- ### InfluxDB: Support for browser access mode removed (should this stay??)
|
||||
|
||||
In the InfluxDB data source, browser access mode was deprecated in grafana 8.0.0 and we are removing this feature in 9.0.0. If you are using this mode, you need to [switch to server access mode]({{< relref "../../datasources/influxdb/##influxql-classic-influxdb-query" >}}) on the data source configuration page or you can do this via provisioning. -->
|
||||
In the InfluxDB data source, browser access mode was deprecated in grafana 8.0.0 and we are removing this feature in 9.0.0. If you are using this mode, you need to [switch to server access mode](../../datasources/influxdb/##influxql-classic-influxdb-query) on the data source configuration page or you can do this via provisioning. -->
|
||||
|
||||
### Transformations: Allow more complex regex expressions in rename by regex
|
||||
|
||||
@@ -90,7 +90,7 @@ The recommendation here is to enable `envelopeEncryption` for older versions, or
|
||||
before upgrading to v9.0. However, the latter is probably going to be removed in one of the next releases, so we hugely
|
||||
encourage to move on with envelope encryption.
|
||||
|
||||
Find [here]({{< relref "../../setup-grafana/configure-security/configure-database-encryption" >}}) more details and some
|
||||
Find [here](../../setup-grafana/configure-security/configure-database-encryption/) more details and some
|
||||
possible workarounds in case you end up in an undesired situation.
|
||||
|
||||
### A note on Grafana Enterprise licensing
|
||||
|
||||
@@ -24,4 +24,4 @@ weight: 2100
|
||||
|
||||
## Technical notes
|
||||
|
||||
Beginning in v9.2, Grafana has a [supported database versions policy]({{< relref "../../setup-grafana/installation#supported-databases" >}}). As of this release, MySQL versions from 5.7, postgres versions from v10, and SQLite 3 are supported databases.
|
||||
Beginning in v9.2, Grafana has a [supported database versions policy](../../setup-grafana/installation/#supported-databases). As of this release, MySQL versions from 5.7, postgres versions from v10, and SQLite 3 are supported databases.
|
||||
|
||||
@@ -28,7 +28,7 @@ weight: 1800
|
||||
|
||||
Beginning in v9.5, the InfluxDB data source deprecates the `database` field in provisioning files.
|
||||
The `dbName` field under `jsonData` must be used to store the database information.
|
||||
For more information and examples, please refer to [InfluxDB Provisioning]({{< relref "../../datasources/influxdb#provision-the-data-source" >}}).
|
||||
For more information and examples, please refer to [InfluxDB Provisioning](../../datasources/influxdb/#provision-the-data-source).
|
||||
|
||||
### Dashboard previews deprecation notice
|
||||
|
||||
@@ -36,4 +36,4 @@ We are deprecating the dashboard previews feature and will remove it in Grafana
|
||||
|
||||
### Migrate your API keys to service accounts
|
||||
|
||||
We are upgrading Grafana [API keys](/docs/grafana/<GRAFANA_VERSION>/administration/service-accounts/migrate-api-keys/) to service accounts. Service accounts are a superset of API keys that include token rotation and compatibility with [Role-based access control]({{< relref "../../administration/roles-and-permissions/access-control" >}}). In a future release, we'll automatically migrate all existing API keys to service accounts. All of your existing tokens will continue to work; they will simply be migrated to service accounts. You can preempt this change by migrating your existing API keys to service accounts using Grafana's UI or API. Learn how to do this in the [API keys documentation](/docs/grafana/<GRAFANA_VERSION>/administration/service-accounts/migrate-api-keys/).
|
||||
We are upgrading Grafana [API keys](/docs/grafana/<GRAFANA_VERSION>/administration/service-accounts/migrate-api-keys/) to service accounts. Service accounts are a superset of API keys that include token rotation and compatibility with [Role-based access control](../../administration/roles-and-permissions/access-control/). In a future release, we'll automatically migrate all existing API keys to service accounts. All of your existing tokens will continue to work; they will simply be migrated to service accounts. You can preempt this change by migrating your existing API keys to service accounts using Grafana's UI or API. Learn how to do this in the [API keys documentation](/docs/grafana/<GRAFANA_VERSION>/administration/service-accounts/migrate-api-keys/).
|
||||
|
||||
Reference in New Issue
Block a user