Plugins on Grafana Labs

Install plugins

Sun, 08 Mar 2026 04:37:10 +0000

Install Grafana plugins

Grafana supports data source, panel, and app plugins. Having panels as plugins makes it easy to create and add any kind of panel, to show your data, or improve your favorite dashboards. Apps enable the bundling of data sources, panels, dashboards, and Grafana pages into a cohesive experience.

In a web browser, navigate to the official Grafana Plugins page and find a plugin that you want to install.
Click the plugin, and then click the Installation tab.

Install plugin on Grafana Cloud

On the Installation tab, in the For field, click the name of the Grafana instance that you want to install the plugin on.

Grafana Cloud handles the plugin installation automatically.

Install plugin on local Grafana

Follow the instructions on the Install tab. You can either install the plugin with a Grafana CLI command or by downloading and uncompress a .zip file into the Grafana plugins directory. We recommend using Grafana CLI in most instances. The .zip option is available if your Grafana server does not have access to the internet.

For more information about Grafana CLI plugin commands, refer to Plugin commands.

As of Grafana v8.0, a plugin catalog app was introduced in order to make managing plugins easier. For more information, refer to Plugin catalog.

Install a packaged plugin

After the user has downloaded the archive containing the plugin assets, they can install it by extracting the archive into their plugin directory.

unzip my-plugin-0.2.0.zip -d YOUR_PLUGIN_DIR/my-plugin

The path to the plugin directory is defined in the configuration file. For more information, refer to Configuration.

Plugin catalog

Sun, 08 Mar 2026 04:37:10 +0000

Plugin catalog

The plugin catalog allows you to browse and manage plugins from within Grafana. Only a Grafana server administrator can access and use the catalog.

Note: The plugin catalog is designed to work with a single Grafana server instance only. Support for Grafana clusters will be added in future Grafana releases.

Your browser does not support the video tag.

Before you can use the plugin catalog, you must enable it in the Grafana configuration file. Before following the steps below, make sure you are logged in as a Grafana administrator.

Browse plugins

To browse available plugins:

In Grafana, navigate to Configuration > Plugins.
Click Install & manage plugins.

You can also browse existing plugins by navigating to the Library tab.

Install a plugin

In Grafana, navigate to Configuration > Plugins.
Click Install & manage plugins.
Browse and find a plugin.
Click on the plugin logo.
Click Install.

A confirmation message opens notifying that the installation was successful.

Update a plugin

In Grafana, navigate to Configuration > Plugins.
Click Install & manage plugins.
Navigate to the Library tab.
Click on the plugin logo.
Click Update.

A confirmation message opens notifying that the installation was successful.

Uninstall a plugin

In Grafana, navigate to Configuration > Plugins.
Click Install & manage plugins.
Navigate to the Library tab.
Click on the plugin logo.
Click Uninstall.

A confirmation message opens notifying that the installation was successful.

Plugin signatures

Sun, 08 Mar 2026 04:37:10 +0000

Plugin signatures

Plugin signature verification (signing) is a security measure to make sure plugins haven’t been tampered with. Upon loading, Grafana checks to see if a plugin is signed or unsigned when inspecting and verifying its digital signature.

At startup, Grafana verifies the signatures of every plugin in the plugin directory. If a plugin is unsigned, then Grafana does not load nor start it. To see the result of this verification for each plugin, navigate to Configuration -> Plugins.

Grafana also writes an error message to the server log:

WARN[05-26|12:00:00] Some plugin scanning errors were found   errors="plugin '<plugin id>' is unsigned, plugin '<plugin id>' has an invalid signature"

If you are a plugin developer and want to know how to sign your plugin, refer to Sign a plugin.

Signature status	Description
Core	Core plugin built into Grafana.
Invalid signature	The plugin has a invalid signature.
Modified signature	The plugin has changed since it was signed. This may indicate malicious intent.
Unsigned	The plugin is not signed.
Signed	The plugin signature was successfully verified.

Plugin signature levels

All plugins is signed under a signature level. The signature level determines how the plugin can be distributed.

Plugin Level	Description
Private	Private plugins are for use on your own Grafana. They may not be distributed to the Grafana community, and are not published in the Grafana catalog.
Community	Community plugins have dependent technologies that are open source and not for profit. Community plugins are published in the official Grafana catalog, and are available to the Grafana community.
Commercial	Commercial plugins have dependent technologies that are closed source or commercially backed. Commercial Plugins are published on the official Grafana catalog, and are available to the Grafana community.

Plugin Level

Description

Private

Private plugins are for use on your own Grafana. They may not be distributed to the Grafana community, and are not published in the Grafana catalog.

Community

Community plugins have dependent technologies that are open source and not for profit.

Community plugins are published in the official Grafana catalog, and are available to the Grafana community.

Commercial

Commercial plugins have dependent technologies that are closed source or commercially backed.

Commercial Plugins are published on the official Grafana catalog, and are available to the Grafana community.

Allow unsigned plugins

We strongly recommend that you don’t run unsigned plugins in your Grafana installation. If you’re aware of the risks and you still want to load an unsigned plugin, refer to Configuration.

If you’ve allowed loading of an unsigned plugin, then Grafana writes a warning message to the server log:

WARN[06-01|16:45:59] Running an unsigned plugin   pluginID=<plugin id>

Note: If you’re developing a plugin, then you can enable development mode to allow all unsigned plugins.