add datasource plugin autohome-compareQueries-datasource V1.0.0

[nfw999]

autohome-compareQueries-datasource is built as a datasource plugin that combines and contrasts different time shifts data.

[nfw999]

Webpack copy of grafana-meta-queries implementing grafana/grafana#2093

This plugin is built as a datasource plugin that combines and contrasts different time shifts data.

Time shift supports the following units: s (seconds), m (minutes), h (hours), d (days), w (weeks), M (months), y (years)

Screenshots

Installation

Clone this project into the grafana plugins directory (if you install grafana with the package, the default is /var / lib / grafana / plugins). Restart grafana and the datasource plugin should be detected and automatically used.

Usage

• Create a datasource and select the Compare Query Datasource plugin.
• Create a basic query
• Create a query use compare query datasource and set base query as compare query
• Add time shift on the compare query

[marcusolsson]

Thank you for your patience while waiting for us to review your plugin.

We're working hard at improving the plugin experience for both users and authors. I'd like to share some important information on how to package and publish plugins going forward.

Since Grafana 7.3, we require all plugins to be signed. By signing your plugin, users can guarantee the integrity of the plugin and that the plugin version they've installed hasn't been modified since it was released. For more information on how to sign your plugin, refer to Sign a plugin.

With this, we now require plugins to be packaged before we publish them. This means that instead of a commit containing a dist directory, you will need to submit a link to a ZIP archive containing your plugin. For more information on how to package your plugin, refer to Package a plugin.

Once you've packaged your plugin, you'll need to update your entry to repo.json to the new format. You can read more on how to do this under Add a plugin to repo.json.

To summarize, to publish your plugin, make sure that you:

1. Sign your plugin
2. Package your plugin
3. Create a new GitHub release and upload the packaged plugin as a release asset
4. Update your repo.json entry

Here's an example of a properly packaged plugin. In the same repository, you can find a GitHub Action that signs, packages, and releases the plugin whenever you create a new tag.

Once you've created a GitHub release with the packaged plugin, you can right-click the release asset, copy the link, and validate it using the plugin validator.

Finally, in the November community call, I'll be walking through the steps needed to sign and package your plugin. A recording will be made available on our YouTube account, in case you can't make it.

[marcusolsson]

Closing due to lack of activity.