<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Introduction on Grafana Labs</title><link>https://grafana.com/docs/learning-hub/plugin-development/01-intro/</link><description>Recent content in Introduction on Grafana Labs</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="/docs/learning-hub/plugin-development/01-intro/index.xml" rel="self" type="application/rss+xml"/><item><title>Journey overview</title><link>https://grafana.com/docs/learning-hub/plugin-development/01-intro/01-journey-overview/</link><pubDate>Wed, 11 Nov 2026 06:29:02 +0100</pubDate><guid>https://grafana.com/docs/learning-hub/plugin-development/01-intro/01-journey-overview/</guid><content><![CDATA[&lt;h1 id=&#34;build-the-plugin-grafana-doesnt-have-yet&#34;&gt;Build the plugin Grafana doesn&amp;rsquo;t have yet&lt;/h1&gt;
&lt;p&gt;While Grafana includes built-in visualizations and data sources, sooner or later you need one that isn&amp;rsquo;t there. A plugin is an add-on you build that extends what Grafana can do. This journey introduces plugin development and shows you how to build a plugin and submit it so other people can install and use it.&lt;/p&gt;
&lt;h2 id=&#34;what-youll-learn&#34;&gt;What you&amp;rsquo;ll learn&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;What a plugin is made of, and which types of plugins you can build&lt;/li&gt;
&lt;li&gt;How to build a plugin with the &lt;code&gt;create-plugin&lt;/code&gt; tool, yourself or with an AI coding assistant&lt;/li&gt;
&lt;li&gt;How to submit your plugin for review and publish it in the Grafana plugin catalog&lt;/li&gt;
&lt;li&gt;How to sell your plugin through the Grafana Marketplace, if you want to&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;journey-duration&#34;&gt;Journey duration&lt;/h2&gt;
&lt;p&gt;About 25 minutes to read the journey. Building your plugin takes longer, depending on your plugin and the tutorial you follow.&lt;/p&gt;
]]></content><description>&lt;h1 id="build-the-plugin-grafana-doesnt-have-yet">Build the plugin Grafana doesn&amp;rsquo;t have yet&lt;/h1>
&lt;p>While Grafana includes built-in visualizations and data sources, sooner or later you need one that isn&amp;rsquo;t there. A plugin is an add-on you build that extends what Grafana can do. This journey introduces plugin development and shows you how to build a plugin and submit it so other people can install and use it.&lt;/p></description></item><item><title>What's a Grafana plugin, and what can you do with it?</title><link>https://grafana.com/docs/learning-hub/plugin-development/01-intro/02-what-can-you-build/</link><pubDate>Wed, 11 Nov 2026 06:29:02 +0100</pubDate><guid>https://grafana.com/docs/learning-hub/plugin-development/01-intro/02-what-can-you-build/</guid><content><![CDATA[&lt;h1 id=&#34;whats-a-grafana-plugin-and-what-can-you-do-with-it&#34;&gt;What&amp;rsquo;s a Grafana plugin, and what can you do with it?&lt;/h1&gt;
&lt;p&gt;A &lt;strong&gt;plugin&lt;/strong&gt; is a folder of code that Grafana loads when it starts. Grafana reads it, registers what the code provides, and runs it so the new capability appears in the interface next to the built-in ones.&lt;/p&gt;
&lt;p&gt;For example, a data source you write is usable in dashboards and Explore. A visualization you write is selectable as a panel on a dashboard.&lt;/p&gt;
&lt;h2 id=&#34;match-your-goal-to-one-of-the-three-plugin-types&#34;&gt;Match your goal to one of the three plugin types&lt;/h2&gt;
&lt;p&gt;With the &lt;code&gt;create-plugin&lt;/code&gt; tool, you can build one of these three things that Grafana can&amp;rsquo;t do today:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A new way to draw data:&lt;/strong&gt; When no built-in visualization shows your data the way you need it, you can add one that appears in the normal panel list. To do this, use a &lt;strong&gt;panel plugin&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Access to a system Grafana can&amp;rsquo;t query yet:&lt;/strong&gt; If it&amp;rsquo;s a database, an API, or another source Grafana can&amp;rsquo;t query yet, you can add it and then use it in dashboards and Explore, and in alert rules if the plugin has a backend component. To do this, use a &lt;strong&gt;data source plugin&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A complete experience:&lt;/strong&gt; Custom pages, and optionally the dashboards and data sources that go with them, in one package. To do this, use an &lt;strong&gt;app plugin&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The tool also offers &lt;strong&gt;App with Scenes&lt;/strong&gt;, an app plugin whose pages are built as dynamic, dashboard-like experiences. Refer to the &lt;a href=&#34;/developers/scenes/&#34;&gt;Grafana Scenes documentation&lt;/a&gt; to learn more.&lt;/p&gt;
]]></content><description>&lt;h1 id="whats-a-grafana-plugin-and-what-can-you-do-with-it">What&amp;rsquo;s a Grafana plugin, and what can you do with it?&lt;/h1>
&lt;p>A &lt;strong>plugin&lt;/strong> is a folder of code that Grafana loads when it starts. Grafana reads it, registers what the code provides, and runs it so the new capability appears in the interface next to the built-in ones.&lt;/p></description></item><item><title>What a plugin is made of</title><link>https://grafana.com/docs/learning-hub/plugin-development/01-intro/03-what-a-plugin-is-made-of/</link><pubDate>Wed, 11 Nov 2026 06:29:02 +0100</pubDate><guid>https://grafana.com/docs/learning-hub/plugin-development/01-intro/03-what-a-plugin-is-made-of/</guid><content><![CDATA[&lt;h1 id=&#34;what-a-plugin-is-made-of&#34;&gt;What a plugin is made of&lt;/h1&gt;
&lt;p&gt;Every plugin includes a &lt;strong&gt;frontend component&lt;/strong&gt; with code that runs in the browser. For a panel plugin, that&amp;rsquo;s all you need: it draws data that Grafana has already fetched.&lt;/p&gt;
&lt;h2 id=&#34;some-plugins-also-need-a-backend-component&#34;&gt;Some plugins also need a backend component&lt;/h2&gt;
&lt;p&gt;A &lt;strong&gt;backend component&lt;/strong&gt; is the part of a plugin that runs on the Grafana server instead of in the browser. Data source and app plugins can have one, and the &lt;code&gt;create-plugin&lt;/code&gt; tool asks whether to add it. Panel plugins can&amp;rsquo;t.&lt;/p&gt;
&lt;p&gt;You need a backend component when the browser is the wrong place to do the work:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The system you&amp;rsquo;re querying isn&amp;rsquo;t reachable from a browser, or it uses a protocol other than HTTP, for example a SQL database server.&lt;/li&gt;
&lt;li&gt;You need to keep credentials such as API keys out of browser code.&lt;/li&gt;
&lt;li&gt;You want a data source to work with Grafana alerting.&lt;/li&gt;
&lt;li&gt;You want to keep state between users, for example to cache query results.&lt;/li&gt;
&lt;/ul&gt;
]]></content><description>&lt;h1 id="what-a-plugin-is-made-of">What a plugin is made of&lt;/h1>
&lt;p>Every plugin includes a &lt;strong>frontend component&lt;/strong> with code that runs in the browser. For a panel plugin, that&amp;rsquo;s all you need: it draws data that Grafana has already fetched.&lt;/p></description></item><item><title>Before you begin</title><link>https://grafana.com/docs/learning-hub/plugin-development/01-intro/04-before-you-begin/</link><pubDate>Wed, 11 Nov 2026 06:29:02 +0100</pubDate><guid>https://grafana.com/docs/learning-hub/plugin-development/01-intro/04-before-you-begin/</guid><content><![CDATA[&lt;h1 id=&#34;before-you-begin&#34;&gt;Before you begin&lt;/h1&gt;
&lt;p&gt;To build and run a plugin locally, you need:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Node.js and a package manager, for every plugin type.&lt;/li&gt;
&lt;li&gt;Docker, which runs the local Grafana instance you&amp;rsquo;ll test against.&lt;/li&gt;
&lt;li&gt;Go and Mage, but only if your plugin has a &lt;strong&gt;backend component&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Optionally, an AI coding assistant, if you choose to build your plugin with AI.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;do-i-need-an-org&#34;&gt;Do I need an org?&lt;/h2&gt;
&lt;p&gt;You need a Grafana Cloud organization where you have the Admin role &lt;strong&gt;only&lt;/strong&gt; if you want to publish a plugin.&lt;/p&gt;
&lt;p&gt;The &lt;code&gt;create-plugin&lt;/code&gt; tool asks for your Grafana Cloud organization name early on and uses it as the first part of your plugin&amp;rsquo;s ID. You can generate, build, and run a plugin locally with a placeholder name, but signing only works when the plugin ID starts with your real organization name. If you plan to publish, enter your real Grafana Cloud organization name from the start so you don&amp;rsquo;t have to rename your plugin later.&lt;/p&gt;
&lt;p&gt;Even if you don&amp;rsquo;t have the Admin role in your organization, complete the learning journey to fully understand the plugin development and publishing cycle.&lt;/p&gt;
]]></content><description>&lt;h1 id="before-you-begin">Before you begin&lt;/h1>
&lt;p>To build and run a plugin locally, you need:&lt;/p>
&lt;ul>
&lt;li>Node.js and a package manager, for every plugin type.&lt;/li>
&lt;li>Docker, which runs the local Grafana instance you&amp;rsquo;ll test against.&lt;/li>
&lt;li>Go and Mage, but only if your plugin has a &lt;strong>backend component&lt;/strong>.&lt;/li>
&lt;li>Optionally, an AI coding assistant, if you choose to build your plugin with AI.&lt;/li>
&lt;/ul>
&lt;h2 id="do-i-need-an-org">Do I need an org?&lt;/h2>
&lt;p>You need a Grafana Cloud organization where you have the Admin role &lt;strong>only&lt;/strong> if you want to publish a plugin.&lt;/p></description></item><item><title>Resources</title><link>https://grafana.com/docs/learning-hub/plugin-development/01-intro/05-plugin-resources/</link><pubDate>Wed, 11 Nov 2026 06:29:02 +0100</pubDate><guid>https://grafana.com/docs/learning-hub/plugin-development/01-intro/05-plugin-resources/</guid><content><![CDATA[&lt;h1 id=&#34;resources&#34;&gt;Resources&lt;/h1&gt;
&lt;p&gt;These pages live in the Plugin Tools documentation portal.&lt;/p&gt;
&lt;h2 id=&#34;documentation&#34;&gt;Documentation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;/developers/plugin-tools/key-concepts/plugin-types-usage&#34;&gt;Plugin types and usage&lt;/a&gt;: The three types, mapped to what they add in Grafana.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;/developers/plugin-tools/key-concepts/anatomy-of-a-plugin&#34;&gt;Anatomy of a plugin&lt;/a&gt;: Config editor, query editor, and the health check.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;/developers/plugin-tools/&#34;&gt;Get started&lt;/a&gt;: How to start a project with &lt;code&gt;create-plugin&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;/developers/plugin-tools/tutorials/build-ai-plugin&#34;&gt;Build a plugin with AI&lt;/a&gt;: Build a data source plugin and an app plugin by prompting an AI coding assistant.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;/developers/plugin-tools/key-concepts/data-frames&#34;&gt;Data frames&lt;/a&gt;: The table-shaped result Grafana visualizes.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;/developers/plugin-tools/reference/cli-commands&#34;&gt;CLI commands&lt;/a&gt;: The &lt;code&gt;create-plugin&lt;/code&gt; prompts, including the App with Scenes type.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;/developers/scenes/&#34;&gt;Scenes library&lt;/a&gt;: The library that allows you to build visual experiences.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;community&#34;&gt;Community&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://community.grafana.com/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Grafana Community Forums&lt;/a&gt;: Share ideas, ask questions.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://slack.grafana.com/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Grafana Slack&lt;/a&gt;: Join the conversation.&lt;/li&gt;
&lt;/ul&gt;
]]></content><description>&lt;h1 id="resources">Resources&lt;/h1>
&lt;p>These pages live in the Plugin Tools documentation portal.&lt;/p>
&lt;h2 id="documentation">Documentation&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="/developers/plugin-tools/key-concepts/plugin-types-usage">Plugin types and usage&lt;/a>: The three types, mapped to what they add in Grafana.&lt;/li>
&lt;li>&lt;a href="/developers/plugin-tools/key-concepts/anatomy-of-a-plugin">Anatomy of a plugin&lt;/a>: Config editor, query editor, and the health check.&lt;/li>
&lt;li>&lt;a href="/developers/plugin-tools/">Get started&lt;/a>: How to start a project with &lt;code>create-plugin&lt;/code>.&lt;/li>
&lt;li>&lt;a href="/developers/plugin-tools/tutorials/build-ai-plugin">Build a plugin with AI&lt;/a>: Build a data source plugin and an app plugin by prompting an AI coding assistant.&lt;/li>
&lt;li>&lt;a href="/developers/plugin-tools/key-concepts/data-frames">Data frames&lt;/a>: The table-shaped result Grafana visualizes.&lt;/li>
&lt;li>&lt;a href="/developers/plugin-tools/reference/cli-commands">CLI commands&lt;/a>: The &lt;code>create-plugin&lt;/code> prompts, including the App with Scenes type.&lt;/li>
&lt;li>&lt;a href="/developers/scenes/">Scenes library&lt;/a>: The library that allows you to build visual experiences.&lt;/li>
&lt;/ul>
&lt;h2 id="community">Community&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://community.grafana.com/" target="_blank" rel="noopener noreferrer">Grafana Community Forums&lt;/a>: Share ideas, ask questions.&lt;/li>
&lt;li>&lt;a href="https://slack.grafana.com/" target="_blank" rel="noopener noreferrer">Grafana Slack&lt;/a>: Join the conversation.&lt;/li>
&lt;/ul></description></item></channel></rss>