- npx @grafana/sign-plugin --rootUrls https://example.com/grafana
- ```
-
-1. After the `rootUrls` flag, enter a comma-separated list of URLs for the Grafana instances where you intend to install the plugin.
-
-## Plugin signature levels
-
-To sign a plugin, you need to select the _signature level_ that you want to sign it under. The signature level of your plugin determines how you can distribute it.
-
-You can sign your plugin under three different _signature levels_: _private_, _community_, and _commercial_.
-
-| **Plugin Level** | **Paid Subscription Required?** | **Description** |
-| ---------------- | ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Private | No;
Free of charge | You can create and sign a Private plugin for any technology at no charge.
Private plugins are intended for use on your own installation of Grafana. They may not be distributed to the Grafana community, and they are not published in the Grafana plugin catalog.
|
-| Community | No;
Free of charge | You can create, sign, and distribute plugins at no charge, provided that all dependent technologies are open source and not for profit.
Community plugins are published in the official Grafana catalog, and are available to the entire Grafana community.
|
-| Commercial | Yes;
Commercial plugin subscription required | You can create, sign, and distribute plugins with dependent technologies that are closed source or commercially backed. To do so, enter into a Commercial plugin subscription with Grafana Labs.
Commercial plugins are published on the Grafana plugin catalog, and are available to the entire Grafana community.
|
-
-For instructions on how to sign a plugin under the Community and Commercial signature level, refer to [Sign a public plugin](#sign-a-public-plugin).
-
-For instructions on how to sign a plugin under the Private signature level, refer to [Sign a private plugin](#sign-a-private-plugin).
-
-## Plugin manifest
-
-For Grafana to verify the digital signature of a plugin, the plugin must include a signed manifest file, `MANIFEST.txt`. The signed manifest file contains two sections:
-
-- **Signed message -** Contains plugin metadata and plugin files with their respective checksums (SHA256).
-- **Digital signature -** Created by encrypting the signed message using a private key. Grafana has a public key built-in that can be used to verify that the digital signature has been encrypted using the expected private key.
-
-**Example**
-
-```txt
------BEGIN PGP SIGNED MESSAGE-----
-Hash: SHA512
-
-{
- "manifestVersion": "2.0.0",
- "signatureType": "community",
- "signedByOrg": "myorgid",
- "signedByOrgName": "My Org",
- "plugin": "myorgid-simple-panel",
- "version": "1.0.0",
- "time": 1602753404133,
- "keyId": "7e4d0c6a708866e7",
- "files": {
- "LICENSE": "12ab7a0961275f5ce7a428e662279cf49bab887d12b2ff7bfde738346178c28c",
- "module.js.LICENSE.txt": "0d8f66cd4afb566cb5b7e1540c68f43b939d3eba12ace290f18abc4f4cb53ed0",
- "module.js.map": "8a4ede5b5847dec1c6c30008d07bef8a049408d2b1e862841e30357f82e0fa19",
- "plugin.json": "13be5f2fd55bee787c5413b5ba6a1fae2dfe8d2df6c867dadc4657b98f821f90",
- "README.md": "2d90145b28f22348d4f50a81695e888c68ebd4f8baec731fdf2d79c8b187a27f",
- "module.js": "b4b6945bbf3332b08e5e1cb214a5b85c82557b292577eb58c8eb1703bc8e4577"
- }
-}
------BEGIN PGP SIGNATURE-----
-Version: OpenPGP.js v4.10.1
-Comment: https://openpgpjs.org
-
-wqEEARMKAAYFAl+IE3wACgkQfk0ManCIZudpdwIHTCqjVzfm7DechTa7BTbd
-+dNIQtwh8Tv2Q9HksgN6c6M9nbQTP0xNHwxSxHOI8EL3euz/OagzWoiIWulG
-7AQo7FYCCQGucaLPPK3tsWaeFqVKy+JtQhrJJui23DAZLSYQYZlKQ+nFqc9x
-T6scfmuhWC/TOcm83EVoCzIV3R5dOTKHqkjIUg==
-=GdNq
------END PGP SIGNATURE-----
-```
-
-## Troubleshooting
-
-### Why do I get a "Modified signature" error?
-
-In some cases an invalid `MANIFEST.txt` is generated because of an issue when signing the plugin on Windows. You can fix this by replacing all double backslashes, `\\`, with a forward slash, `/`, in the `MANIFEST.txt` file. You need to do this every time you sign your plugin.
-
-### Why do I get a "Field is required: `rootUrls`" error for my public plugin?
-
-With a **public** plugin, your plugin doesn't have a plugin signature level assigned to it yet. A Grafana team member will assign a signature level to your plugin once it has been reviewed and approved. For more information, refer to [Sign a public plugin](#sign-a-public-plugin).
-
-### Why do I get a "Field is required: `rootUrls`" error for my private plugin?
-
-With a **private** plugin, you need to add a `rootUrls` flag to the `plugin:sign` command. The `rootUrls` must match the [root_url]({{< relref "../../setup-grafana/configure-grafana/#root_url" >}}) configuration. For more information, refer to [Sign a private plugin](#sign-a-private-plugin).
-
-If you still get this error, make sure that the API key was generated by a Grafana Cloud account that matches the first part of the plugin ID.
diff --git a/docs/sources/developers/plugins/working-with-data-frames.md b/docs/sources/developers/plugins/working-with-data-frames.md
deleted file mode 100644
index 89f68ebd957..00000000000
--- a/docs/sources/developers/plugins/working-with-data-frames.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: Work with data frames
----
-
-# Work with data frames
-
-The [data frame]({{< relref "data-frames" >}}) is a columnar data structure that allows for efficient querying of large amounts of data. Since data frames are a central concept when developing plugins for Grafana, in this guide we'll look at some ways you can use them.
-
-The `DataFrame` interface contains a `name` and an array of `fields` where each field contains the name, type, and the values for the field.
-
-> **Note:** If you want to migrate an existing plugin to use the data frame format, refer to [Migrate to data frames]({{< relref "migration-guide/#migrate-to-data-frames" >}}).
-
-## Create a data frame
-
-If you build a data source plugin, then you'll most likely want to convert a response from an external API to a data frame. Let's look at how to do this.
-
-Let's start with creating a simple data frame that represents a time series. The easiest way to create a data frame is to use the `toDataFrame` function.
-
-```ts
-// Need to be of the same length.
-const timeValues = [1599471973065, 1599471975729];
-const numberValues = [12.3, 28.6];
-
-// Create data frame from values.
-const frame = toDataFrame({
- name: 'http_requests_total',
- fields: [
- { name: 'Time', type: FieldType.time, values: timeValues },
- { name: 'Value', type: FieldType.number, values: numberValues },
- ],
-});
-```
-
-> **Note:** Data frames representing time series contain at least a `time` field and a `number` field. By convention, built-in plugins use `Time` and `Value` as field names for data frames containing time series data.
-
-As you can see from the example, to create data frames like this, your data must already be stored as columnar data. If you already have the records in the form of an array of objects, then you can pass it to `toDataFrame`. In this case, `toDataFrame` tries to guess the schema based on the types and names of the objects in the array. To create complex data frames this way, be sure to verify that you get the schema you expect.
-
-```ts
-const series = [
- { Time: 1599471973065, Value: 12.3 },
- { Time: 1599471975729, Value: 28.6 },
-];
-
-const frame = toDataFrame(series);
-frame.name = 'http_requests_total';
-```
-
-## Read values from a data frame
-
-When you're building a panel plugin, the data frames returned by the data source are available from the `data` prop in your panel component.
-
-```ts
-function SimplePanel({ data: Props }) {
- const frame = data.series[0];
-
- // ...
-}
-```
-
-Before you start reading the data, think about what data you expect. For example, to visualize a time series you need at least one time field and one number field.
-
-```ts
-const timeField = frame.fields.find((field) => field.type === FieldType.time);
-const valueField = frame.fields.find((field) => field.type === FieldType.number);
-```
-
-Other types of visualizations might need multiple dimensions. For example, a bubble chart that uses three numeric fields: the X-axis, Y-axis, and one for the radius of each bubble. In this case, instead of hard coding the field names, we recommend that you let the user choose the field to use for each dimension.
-
-```ts
-const x = frame.fields.find((field) => field.name === xField);
-const y = frame.fields.find((field) => field.name === yField);
-const size = frame.fields.find((field) => field.name === sizeField);
-
-for (let i = 0; i < frame.length; i++) {
- const row = [x?.values.get(i), y?.values.get(i), size?.values.get(i)];
-
- // ...
-}
-```
-
-Alternatively, you can use the `DataFrameView`, which gives you an array of objects that contain a property for each field in the frame.
-
-```ts
-const view = new DataFrameView(frame);
-
-view.forEach((row) => {
- console.log(row[options.xField], row[options.yField], row[options.sizeField]);
-});
-```
-
-## Display values from a data frame
-
-Field options let the user control how Grafana displays the data in a data frame.
-
-To apply the field options to a value, use the `display` method on the corresponding field. The result contains information such as the color and suffix to use when display the value.
-
-```ts
-const valueField = frame.fields.find((field) => field.type === FieldType.number);
-
-return (
-
- {valueField
- ? valueField.values.toArray().map((value) => {
- const displayValue = valueField.display!(value);
- return (
-
- {displayValue.text} {displayValue.suffix ? displayValue.suffix : ''}
-
- );
- })
- : null}
-