IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-02-11 08:05:43 -06:00
Code Issues Packages Projects Releases Wiki Activity

Fix broken relrefs (#57092)

Browse Source 
* Fixes relrefs

* Fixes more relrefs
This commit is contained in:
brendamuir 2022-10-17 16:54:00 +01:00 committed by GitHub
parent 2bed451990
commit b7feb34acf
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/sources/alerting/alerting-rules/_index.md
View File

@ -20,8 +20,8 @@ You can:
- [Create Grafana Mimir or Loki managed recording rules]({{< relref "create-mimir-loki-managed-recording-rule/" >}})
- [Edit Grafana Mimir or Loki rule groups and namespaces]({{< relref "edit-mimir-loki-namespace-group/" >}})
- [Create Grafana managed alert rules]({{< relref "create-grafana-managed-rule/" >}})
- [View the state and health of alert rules]({{< relref "../fundamentals/state-and-health/" >}})
- [View and filter alert rules]({{< relref "rule-list/" >}})
- [View the state and health of alert rules]({{< relref "../view-state-health/" >}})
- [View and filter alert rules]({{< relref "../view-alert-rules/" >}})
**Note:**
Grafana managed alert rules can only be edited or deleted by users with Edit permissions for the folder storing the rules.

2
docs/sources/alerting/fundamentals/evaluate-grafana-alerts.md
View File

@ -28,7 +28,7 @@ Grafana managed alerts query the following backend data sources that have alerti
### 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-rules/rule-list/" >}}).
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 "../view-state-health/" >}}).
| Metric Name | Type | Description |
| ------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------- |

0
docs/sources/alerting/view-alert rules/_index.md → docs/sources/alerting/view-alert-rules/index.md
View File

0
docs/sources/alerting/view-state-health/_index.md → docs/sources/alerting/view-state-health/index.md
View File

2
docs/sources/fundamentals/timeseries-dimensions/index.md
View File

@ -86,7 +86,7 @@ In this case the labels that represent the dimensions will have two keys based o
> **Note:** More than one dimension is currently only supported in the Logs queries within the Azure Monitor service as of version 7.1.
> **Note:** Multiple dimensions are not supported in a way that maps to multiple alerts in Grafana, but rather they are treated as multiple conditions to a single alert. For more information, see See the documentation on [creating alerts with multiple series]({{< relref "../alerting/alerting-rules/create-grafana-managed-rule/#single-and-multi-dimensional-rule" >}}).
> **Note:** Multiple dimensions are not supported in a way that maps to multiple alerts in Grafana, but rather they are treated as multiple conditions to a single alert. For more information, see See the documentation on [creating alerts with multiple series]({{< relref "../../alerting/alerting-rules/create-grafana-managed-rule/#single-and-multi-dimensional-rule" >}}).
### Multiple values