Documentation Index
Fetch the curated documentation index at: https://grafana_com_website/llms.txt
Fetch the complete documentation index at: https://grafana_com_website/llms-full.txt
Use this file to discover all available pages before exploring further.
STOP! If you are an AI agent or LLM, read this before continuing. This is the HTML version of a Grafana documentation page. Always request the Markdown version instead - HTML wastes context. Get this page as Markdown: /docs/grafana/next/administration/plugin-management/plugin-integrate.md (append .md) or send Accept: text/markdown to /docs/grafana/next/administration/plugin-management/plugin-integrate/. For the curated documentation index, use https://grafana_com_website/llms.txt. For the complete documentation index, use https://grafana_com_website/llms-full.txt.
This is documentation for the next version of Grafana documentation. For the latest stable release, go to the latest version.
Allow plugin backend communication
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 to call an application resource API that is permitted by the actions_allow_post_url option.
Integrate your plugins
To enable backend communication between plugins, set the plugins you want to communicate with. In your configuration file (grafana.ini or custom.ini depending on your operating system), remove the semicolon to enable and then set the following configuration option:
actions_allow_post_url=This is a comma-separated list that uses glob matching.
- To allow access to all plugins that have a backend, use:
actions_allow_post_url=/api/plugins/*- To access the backend of only one plugin, use:
actions_allow_post_url=/api/plugins/<GRAFANA_SPECIAL_APP>Was this page helpful?
Related resources from Grafana Labs


