public/grafana
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs: Sync all doc changes in main to v8.0.x (#35333)

Browse Source
This commit is contained in:
Torkel Ödegaard
2021-06-07 18:38:48 +02:00
committed by GitHub
parent df42e49d06
commit 6362bb2f36
131 changed files with 4809 additions and 485 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/developers/plugins/backend/_index.md
+1 -1
View File
@@ -12,7 +12,7 @@ However, one limitation with these plugins are that they execute on the client-s
We use the term _backend plugin_ to denote that a plugin has a backend component. Still, normally a backend plugin requires frontend components as well. This is for example true for backend data source plugins which normally need configuration and query editor components implemented for the frontend.
Data source plugins can be extended with a backend component. In the future we plan to support additional types and possibly new kinds of plugins, such as [notifiers for Grafana Alerting]({{< relref "../../../alerting/notifications.md" >}}) and custom authentication to name a few.
Data source plugins can be extended with a backend component. In the future we plan to support additional types and possibly new kinds of plugins, such as [notifiers for Grafana Alerting]({{< relref "../../../alerting/old-alerting/notifications.md" >}}) and custom authentication to name a few.
## Use cases for implementing a backend plugin