[v10.1.x] Remove plugins (#75585)

* Delete plugins files comprehensively * [publish-technical-documentation-release] Publish from grafana/grafana:v10.1.x/docs/sources * Cleanup whitespace Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * [publish-technical-documentation-next] Publish from grafana/beyla:main/docs/sources * Fix all links to "Sign a plugin" pages Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * [publish_dashboards] * Fix metadata links Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * [publish-technical-documentation-next] Publish from grafana/agent:main/docs/sources * Fix data-frames redirect Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * add collapse shortcode (#15422) * Add note about missing rewrites Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix all data-frames links Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix links to "plugins" Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix links to angular-react Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix "plugin-sdk-go" links Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix backend links Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix "Add query editor help" links Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix some remaining links Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix some stray links Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * [publish_plugins] * Add missing redirects and fix a couple more links Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Use partial URLs to appease `doc-validator` for now Signed-off-by: Jack Baldry <jack.baldry@grafana.com> --------- Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
2023-09-27 18:22:15 +01:00
parent a68c3cf9f4
commit ab5939c64c
29 changed files with 59 additions and 66 deletions
@@ -89,7 +89,7 @@ You can assign data source permissions to users, teams, and roles which will all

 When you enable query and resource caching, Grafana temporarily stores the results of data source queries and resource requests. When you or another user submit the same query or resource request again, the results will come back from the cache instead of from the data source.

-When using Grafana, a query pertains to a request for data frames to be modified or displayed. A resource relates to any HTTP requests made by a plugin, such as the Amazon Timestream plugin requesting a list of available databases from AWS. For more information on data source queries and resources, please see the developers page on [backend plugins]({{< relref "../../developers/plugins/introduction-to-plugin-development/backend/" >}}).
+When using Grafana, a query pertains to a request for data frames to be modified or displayed. A resource relates to any HTTP requests made by a plugin, such as the Amazon Timestream plugin requesting a list of available databases from AWS. For more information on data source queries and resources, please see the developers page on [backend plugins](/developers/plugin-tools/introduction/backend-plugins).

 The caching feature works for **all** backend data sources. You can enable the cache globally in Grafana's [configuration]({{< relref "../../setup-grafana/configure-grafana/enterprise-configuration/#caching" >}}), and configure a cache duration (also called Time to Live, or TTL) for each data source individually.

@@ -124,7 +124,7 @@ Query caching works for Grafana's [built-in data sources]({{< relref "../../data
 To verify that a data source works with query caching, follow the [instructions below](#enable-and-configure-query-caching) to **Enable and Configure query caching**. If caching is enabled in Grafana but the Caching tab is not visible for the given data source, then query caching is not available for that data source.

 {{% admonition type="note" %}}
-Some data sources, such as Elasticsearch, Prometheus, and Loki, cache queries themselves, so Grafana _query_ caching does not significantly improve performance. However, _resource_ caching may help. See the developers page on [plugin resources]({{< relref "../../developers/plugins/introduction-to-plugin-development/backend/#resources" >}}) for details.
+Some data sources, such as Elasticsearch, Prometheus, and Loki, cache queries themselves, so Grafana _query_ caching does not significantly improve performance. However, _resource_ caching may help. See the developers page on [plugin resources](/developers/plugin-tools/introduction/backend-plugins#resources) for details.
 {{% /admonition %}}

 ### Enable and configure query caching