Skip to main content
caution

Each submitted plugin is manually reviewed by the Grafana Plugins team. Following best practices or providing a test environment does not guarantee the approval of a submitted plugin. The Grafana Plugins team studies each submission individually and decides on a case-by-case basis.

Refer to Plugin submission review for more details.

Publish a plugin: Frequently asked questions

Do I need to submit a private plugin?​

  • No. Please only submit plugins that you wish to make publicly available for the Grafana community.

How long does it take to review a submission?​

  • We're not able to give an estimate because each plugin submission is unique, though we're constantly working to improve the time it takes to review a plugin. Providing a provisioned test environment can drastically speed up your review.

Can I decide a date when my plugin will be published?​

  • No. We cannot guarantee specific publishing dates, as plugins are immediately published after a review based on our internal prioritization.

Can I see metrics of my plugin installs, downloads or usage?​

  • No. We don't offer this information at the moment to plugin authors.

How can I update my plugin's catalog page?​

  • The plugin's catalog page content is extracted from the plugin README file. To update the plugin's catalog page, submit an updated plugin with the new content included in the README file.

Can I unlist a plugin?​

  • In the event of a bug, unlisting the plugin from our catalog may be possible in exceptional cases, such as security concerns. However, we don't have control over the instances where the plugin is installed.

  • Also, refer to the Grafana Labs Plugin Deprecation Policy to learn more about plugin deprecation.

Can I distribute my plugin somewhere else other than the Grafana plugin catalog?​

  • The official method for distributing Grafana plugins is through our catalog. Alternative methods, such as installing private or development plugins on local Grafana instances, are available as per the guidelines provided in this guide.

Can I still use Angular for a plugin?​

Can I submit plugins built with Toolkit?​

  • The @grafana/toolkit tool is deprecated. Please migrate to create-plugin. In the future, we will reject submissions based on @grafana/toolkit as it becomes increasingly out-of-date.

Do all plugins require signatures?​

  • All plugins require signatures unless they are in development or being submitted to review for the first time.

Do plugin signatures expire?​

  • Plugin signatures do not currently expire.

What source code URL formats are supported?​

  • Using a tag or branch: https://github.com/grafana/clock-panel/tree/v2.1.3
  • Using a tag or branch and the code is in a subdirectory (important for mono repos): https://github.com/grafana/clock-panel/tree/v2.1.3/plugin/ (here, the plugin contains the plugin code)
  • Using the latest main or master branch commit: https://github.com/grafana/clock-panel/ (not recommended, it's better to pass a tag or branch)