Package a plugin
You’ve just built your first plugin, and now you want to share it with the world. In this guide, you’ll learn how to package and share your plugin with others.
For Grafana to be able to load a plugin, it first needs to be built. When you build a plugin from source, a
dist directory is created that contains the production build, or plugin assets, for your plugin.
When the Grafana server starts, it recursively looks in the plugin directory for any directory that contains a
plugin.json file and tries to load the plugin assets in the same directory.
There are three steps needed to package a plugin:
- Building the plugin
- Signing the plugin
- Archiving the plugin
Build the plugin
yarn install --pure-lockfile yarn build
(Optional) If your data source plugin has a backend plugin, build it as well.
Create a ZIP archive of the
mv dist/ myorg-simple-panel zip myorg-simple-panel-1.0.0.zip myorg-simple-panel -r
Publish your plugin on Grafana.com
The best way to share your plugin with the world is to publish it on Grafana Plugins . By having your plugin published on Grafana.com, more users will be able to discover your plugin.
Related Grafana video resources
All about Grafana plugins: Visualizing disparate data sources in one place
Grafana Enterprise plugins are integrations with other commercial monitoring tools (such as Datadog, Splunk, New Relic, ServiceNow, Oracle, and Dynatrace) that are created, maintained, and supported by the Grafana Labs team.
Demo: Getting started with Grafana Enterprise and observability
Join the Grafana Labs team for a 30-minute demo of how to get started with the Grafana Stack, so you can go from zero to observability in just a few minutes.