opensource/grafana
1
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-07-28 08:52:07 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update alert doc structure (#34659)

Browse Source 
* Restructured and fixed broken relrefs.

* Added relrefs.

* created shared alerts section.
This commit is contained in:
achatterjee-grafana
2021-05-25 10:51:28 -04:00
committed by GitHub
parent 0f4806db8a
commit adbe383456
19 changed files with 95 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/sources/developers/plugins/backend/_index.md
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