0e2b741fc3
* Remove old plugin docs, add redirects to new dev portal * Restore plugin.schema.json file * Update docs/sources/administration/plugin-management/index.md Co-authored-by: Jack Baldry <jack.baldry@grafana.com> * More updates * Cleanup links * Update docs/sources/alerting/fundamentals/evaluate-grafana-alerts.md Co-authored-by: Jack Baldry <jack.baldry@grafana.com> * fix codeowners * Change reference links to inline links to avoid 404s * Update docs/sources/datasources/_index.md Co-authored-by: Jack Baldry <jack.baldry@grafana.com> * Update docs/sources/datasources/mysql/_index.md Co-authored-by: Jack Baldry <jack.baldry@grafana.com> * Update docs/sources/datasources/postgres/_index.md Co-authored-by: Jack Baldry <jack.baldry@grafana.com> * Update docs/sources/fundamentals/timeseries-dimensions/index.md Co-authored-by: Jack Baldry <jack.baldry@grafana.com> * Update docs/sources/fundamentals/dashboards-overview/index.md Co-authored-by: Jack Baldry <jack.baldry@grafana.com> * Update docs/sources/fundamentals/dashboards-overview/index.md Co-authored-by: Jack Baldry <jack.baldry@grafana.com> * Update docs/sources/panels-visualizations/configure-standard-options/index.md Co-authored-by: Jack Baldry <jack.baldry@grafana.com> * Update docs/sources/panels-visualizations/query-transform-data/transform-data/index.md Co-authored-by: Jack Baldry <jack.baldry@grafana.com> * Remove grafana.com from 2 URLs * Fix 1 more reference link * Prettier fix --------- Co-authored-by: Jack Baldry <jack.baldry@grafana.com>
3.2 KiB
| labels | title | ||||
|---|---|---|---|---|---|
|
Grafana managed alerts |
Clustering
The current alerting system doesn't support high availability. Alert notifications are not deduplicated and load balancing is not supported between instances; for example, silences from one instance will not appear in the other.
Alert evaluation
Grafana managed alerts are evaluated by the Grafana backend. Rule evaluations are scheduled, according to the alert rule configuration, and queries are evaluated by an engine that is part of core Grafana.
Alerting rules can only query backend data sources with alerting enabled:
- builtin or developed and maintained by grafana:
Graphite,Prometheus,Loki,InfluxDB,Elasticsearch,Google Cloud Monitoring,Cloudwatch,Azure Monitor,MySQL,PostgreSQL,MSSQL,OpenTSDB,Oracle, andAzure Data Explorer - any community backend data sources with alerting enabled (
backendandalertingproperties are set in the plugin.json
Metrics from the alerting engine
The alerting engine publishes some internal metrics about itself. You can read more about how Grafana publishes [internal metrics]({{< relref "../../setup-grafana/set-up-grafana-monitoring/" >}}). See also, [View alert rules and their current state]({{< relref "../../alerting/fundamentals/state-and-health/" >}}).
| Metric Name | Type | Description |
|---|---|---|
alerting.alerts |
gauge | How many alerts by state |
alerting.request_duration_seconds |
histogram | Histogram of requests to the Alerting API |
alerting.active_configurations |
gauge | The number of active, non default alertmanager configurations for grafana managed alerts |
alerting.rule_evaluations_total |
counter | The total number of rule evaluations |
alerting.rule_evaluation_failures_total |
counter | The total number of rule evaluation failures |
alerting.rule_evaluation_duration_seconds |
histogram | The time to evaluate a rule |
alerting.rule_process_evaluation_duration_seconds |
histogram | The time to process the evaluation results for a rule |
alerting.rule_send_alerts_duration_seconds |
histogram | The time to send the alerts to Alertmanager |
alerting.rule_group_rules |
gauge | The number of rules |
alerting.state_calculation_duration_seconds |
histogram | The duration of calculation of a single state |