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

Prettier

Browse Source
This commit is contained in:
Anna Urbiztondo
2025-08-14 10:37:20 +02:00
parent eecb42f5d2
commit 8a3c6ab21c
3 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/administration/plugin-management/customize-nav-bar.md
+1 -2
View File
@@ -5,7 +5,6 @@ labels:
products:
- enterprise
- oss
- cloud
keywords:
- grafana
- plugins
@@ -75,7 +74,7 @@ org-example-app = explore 50
## Find page paths
To move individual pages you need to know their paths. To identify a plugin page path:
To move individual pages you need to know their paths. To identify a plugin page path:
- Visit the page in the browser and check the URL in the address bar.
- Page paths in app plugins follow the format `/a/PLUGIN_ID/PAGE_PATH`
docs/sources/administration/plugin-management/plugin-install.md
+1 -1
View File
@@ -45,7 +45,7 @@ The path to the plugin directory is defined in the configuration file. For more
This feature requires Grafana 11.5.0 or later.
{{< /admonition >}}
You can install plugins by adding the plugin ID to the `plugins.preinstall` section in the Grafana configuration file. This prevents the plugin from being accidentally uninstalled and can be auto-updated. For more information, refer to [Configuration](https://grafana.com/docs/grafana/<GRAFANA_VERSION>/setup-grafana/configure-grafana/#plugins).
You can install plugins by adding the plugin ID to the `plugins.preinstall` section in the Grafana configuration file. This prevents the plugin from being accidentally uninstalled and can be auto-updated. For more information, refer to [Configuration](https://grafana.com/docs/grafana/<GRAFANA_VERSION>/setup-grafana/configure-grafana/#preinstall).
## Install a plugin in air-gapped environment
docs/sources/administration/plugin-management/plugin-integrate.md
+1 -1
View File
@@ -20,7 +20,7 @@ weight: 350
# Allow plugin backend communication
By default, you can only communicate with plugin backends remotely.
By default, you can only communicate with plugin backends remotely.
However, you can configure your Grafana instance to let the frontends of installed plugins to directly communicate with the backends of other plugins installed locally. You can use this configuration to, for example, enable a [canvas panel](https://grafana.com/docs/grafana/<GRAFANA_VERSION>/panels-visualizations/visualizations/canvas/) to call an application resource API that is permitted by the `actions_allow_post_url` option.