content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
# Stale alert instances An alert instance is considered \*\*stale\*\* if the alert rule query returns data but its dimension (or series) has disappeared for a number of consecutive evaluation intervals (2 by default). This is different from the [\*\*No Data\*\* state](ref:no-data-state), which occurs when the alert rul... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/alert-rule-evaluation/stale-alert-instances.md | main | grafana | [
-0.028435932472348213,
-0.0030427374877035618,
0.015883848071098328,
0.10419175773859024,
0.05077580735087395,
-0.04347289726138115,
0.047301653772592545,
-0.08646325767040253,
0.09543341398239136,
-0.06360654532909393,
0.029151758179068565,
-0.06703213602304459,
0.04453935846686363,
-0.04... | 0.042767 |
# Alert rule state and health Each alert rule can generate one or more alert instances—one alert instance for each series or dimension, as shown in the [multi-dimensional alert example](ref:example-multi-dimensional-alerts). Each alert instance of the same alert rule represents a different target and can be in a differ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/alert-rule-evaluation/alert-rule-state-and-health.md | main | grafana | [
0.006088707130402327,
0.020230690017342567,
0.007654928602278233,
0.04822304844856262,
0.14823611080646515,
-0.05079660937190056,
0.09958702325820923,
-0.03492693230509758,
0.09624338895082474,
-0.06491952389478683,
-0.015694016590714455,
-0.02751154452562332,
0.11435878276824951,
0.059737... | 0.096011 |
# Alert rule evaluation The criteria determining when an alert rule fires are based on three settings: - [Evaluation group](#evaluation-group): how frequently the alert rule is evaluated. - [Pending period](#pending-period): how long the condition must be met to start firing. - [Keep firing for](#pending-period): how l... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/alert-rule-evaluation/_index.md | main | grafana | [
-0.07634639739990234,
0.059010207653045654,
-0.020522937178611755,
0.04961877688765526,
0.06053318828344345,
-0.051090043038129807,
0.02407444827258587,
-0.042689625173807144,
0.05947223678231239,
-0.00928796362131834,
-0.021982332691550255,
-0.05773387476801872,
0.04540051147341728,
0.045... | 0.09071 |
\*\*Normal\*\* state and is marked as \*\*Resolved\*\*. - If the alert condition is met again, the alert transitions back to the \*\*Alerting\*\* state, and no new notifications are sent. You can also set the \*\*Keep firing for\*\* period to zero to skip the \*\*Recovering\*\* state entirely. ## Evaluation example Kee... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/alert-rule-evaluation/_index.md | main | grafana | [
-0.04728427529335022,
-0.015752702951431274,
0.04768012464046478,
0.0787733718752861,
0.051447585225105286,
-0.03560066595673561,
0.10620956122875214,
-0.07574156671762466,
0.07928494364023209,
-0.01656721904873848,
-0.0269476268440485,
-0.0567442812025547,
0.09238043427467346,
0.013240629... | 0.094667 |
# Contact points Contact points contain the configuration for sending alert notifications. You can assign a contact point either in the alert rule or notification policy options. A contact point includes one or more contact point integrations for sending alert notifications, such as: {{< column-list >}} - Alertmanager ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/notifications/contact-points.md | main | grafana | [
-0.08679914474487305,
-0.03981931507587433,
-0.05048021674156189,
0.021064648404717445,
0.07986211031675339,
-0.01364955585449934,
0.08205437660217285,
0.0025658158119767904,
0.07459387183189392,
-0.007538931909948587,
-0.02251802198588848,
-0.0701567605137825,
0.06466902047395706,
0.03491... | 0.157084 |
# Group alert notifications Grouping in Grafana Alerting allows you to batch relevant alerts together into a smaller number of notifications. This is particularly important if notifications are delivered to first-responders, such as engineers on-call, where receiving lots of notifications in a short period of time can ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/notifications/group-alert-notifications.md | main | grafana | [
-0.09128992259502411,
-0.02975575067102909,
-0.009625216946005821,
0.03887287154793739,
0.007924326695501804,
-0.05141018331050873,
0.06844589114189148,
-0.03517245873808861,
0.08068539947271347,
-0.03734734654426575,
0.0008933576755225658,
-0.026488322764635086,
0.03454042226076126,
-0.00... | 0.109321 |
a new group of alerts. This option helps reduce the number of notifications sent for related alerts occurring within a short time frame. The longer the group wait, the more time other alerts have to be included in the initial notification of the new group. The shorter the group wait, the earlier the first notification ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/notifications/group-alert-notifications.md | main | grafana | [
-0.015443876385688782,
0.004587439354509115,
0.02941085398197174,
0.013074121437966824,
0.0639464482665062,
-0.03700687736272812,
0.14642253518104553,
-0.1011512279510498,
0.11116688698530197,
-0.0739145278930664,
0.009934878908097744,
-0.05962631106376648,
0.07756807655096054,
-0.00675039... | 0.145389 |
do not send notification. | | 10:50\\* | | `backend` | 4 | Group interval elapsed and resets timer. Send one notification reporting 4 alerts. | \*\*How it works\*\* Once the first notification has been sent for a new group of alerts, the group interval timer starts. When the group interval timer elapses, the system res... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/notifications/group-alert-notifications.md | main | grafana | [
-0.021625708788633347,
-0.041769012808799744,
-0.00874379649758339,
0.056803394109010696,
0.013749917037785053,
-0.022061094641685486,
0.08918645977973938,
-0.07361139357089996,
0.09480932354927063,
-0.07433196902275085,
0.024775110185146332,
-0.038678739219903946,
0.09858547896146774,
-0.... | 0.156101 |
# Notification policies Notification policies provide you with a flexible way of designing how to handle notifications and minimize alert noise. Using label matchers, alert instances are [routed to notification policies](#routing). The notification policy can then [group multiple alert instances into a single notificat... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/notifications/notification-policies.md | main | grafana | [
-0.07455387711524963,
0.006192885804921389,
0.05611296743154526,
0.02211908996105194,
0.151813343167305,
-0.037403833121061325,
0.19705934822559357,
-0.01857290416955948,
0.06897325813770294,
-0.018866660073399544,
-0.01011405698955059,
-0.02770434133708477,
0.09808070212602615,
0.05409022... | 0.145853 |
refer to our [Getting Started with Alert Instances and Notification Routing tutorial](https://grafana.com/tutorials/alerting-get-started-pt2/). {{< /admonition >}} ## Routing To determine which notification policies handle an alert instance, the system looks for matching policies starting from the top of the tree—begin... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/notifications/notification-policies.md | main | grafana | [
-0.06472483277320862,
0.02495526894927025,
0.03605307266116142,
0.03365015611052513,
0.08418942987918854,
-0.080066978931427,
0.060624707490205765,
-0.07586053758859634,
0.08386217057704926,
0.01525693666189909,
-0.018865292891860008,
-0.015178498812019825,
0.0052681961096823215,
0.0457818... | 0.093397 |
child policy. | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/notifications/notification-policies.md | main | grafana | [
-0.04461141675710678,
0.09913221001625061,
0.00034626596607267857,
0.011265316978096962,
0.05953625962138176,
0.03902587294578552,
0.07982159405946732,
-0.04307320713996887,
-0.03199688345193863,
0.08764810115098953,
0.1237342581152916,
0.08119507133960724,
-0.04282079264521599,
0.03511499... | 0.065148 |
# Notifications Choosing how, when, and where to send your alert notifications is an important part of setting up your alerting system. These decisions have a direct impact on your team’s ability to receive the necessary information to resolve issues quickly and minimize alert noise. Start defining your [contact points... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/notifications/_index.md | main | grafana | [
-0.05249873176217079,
-0.06776165962219238,
0.014259005896747112,
0.05281027406454086,
0.14148341119289398,
-0.030802486464381218,
0.1120867133140564,
0.007907778955996037,
0.09754592180252075,
-0.026074916124343872,
-0.036724623292684555,
-0.0017606142209842801,
0.0872885137796402,
0.0873... | 0.123988 |
useful as you and your team refine your initial alerting system. For instance, you can customize notifications with shared [templates](ref:templates) that provide actionable alert information and can be reused for multiple notifications. Additionally, you can use [silences](ref:silences) and [mute timings](ref:mute-tim... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/notifications/_index.md | main | grafana | [
-0.07233621925115585,
0.04138462245464325,
-0.0251212939620018,
0.05130217224359512,
0.07243386656045914,
-0.08560538291931152,
0.08474356681108475,
-0.05872829258441925,
0.05449261516332626,
-0.02877158112823963,
-0.030027732253074646,
-0.04317256808280945,
0.05108017474412918,
0.02596573... | 0.251298 |
# Queries and conditions In Grafana, queries fetch and transform data from data sources, which include databases like MySQL or PostgreSQL, time series databases like Prometheus or InfluxDB, and services like Amazon CloudWatch or Azure Monitor. An alert rule defines the following components: - A [query](#data-source-que... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/alert-rules/queries-conditions.md | main | grafana | [
-0.10199962556362152,
0.006468541920185089,
-0.047532785683870316,
0.058753833174705505,
0.014071106910705566,
-0.10400689393281937,
0.08427415788173676,
-0.06936770677566528,
0.0534830242395401,
0.01287071406841278,
-0.019011663272976875,
-0.03482285887002945,
0.05935867875814438,
-0.0424... | 0.168445 |
math functions/operations on time series data and numbers. For example, `$A + 1` or `$A \* 100`. If queries being compared have \*\*multiple series in their results\*\*, series from different queries are matched(joined) if they have the same labels. For example: {{< docs/shared lookup="alerts/math-example.md" source="g... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/alert-rules/queries-conditions.md | main | grafana | [
-0.11952703446149826,
0.053252190351486206,
-0.07526906579732895,
0.04378780722618103,
-0.08007492870092392,
-0.038337450474500656,
0.058349598199129105,
0.015164719894528389,
0.07440956681966782,
-0.04879907891154289,
-0.06498204171657562,
-0.09239813685417175,
0.051050517708063126,
-0.00... | 0.122473 |
-> 1010 triggers a firing alert. - 1010 -> 990 does not resolve the alert, keeping it in the firing state. - 990 -> 1020 keeps the alert in the firing state. The recovery threshold mitigates unnecessary alert state changes and reduces alert noise. {{< collapse title="Classic condition (legacy)" >}} #### Classic conditi... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/alert-rules/queries-conditions.md | main | grafana | [
-0.05704164505004883,
0.08105133473873138,
0.06037304177880287,
0.024813460186123848,
0.10798866301774979,
-0.01149447076022625,
0.043616361916065216,
0.035222768783569336,
0.02072756178677082,
-0.06642217934131622,
-0.02718067355453968,
0.019645163789391518,
-0.003726943163201213,
-0.0170... | 0.111948 |
# Labels and annotations Labels and annotations add additional information about an alert using key/value pairs: - [Labels](#labels) are used to differentiate an alert from all other alerts and decide how to manage them. - [Annotations](#annotations) provide extra details for alert responders to help them understand an... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/alert-rules/annotation-label.md | main | grafana | [
-0.04033568874001503,
0.037080664187669754,
-0.04598992317914963,
0.06857886165380478,
0.1130199134349823,
-0.014850284904241562,
0.14784090220928192,
-0.03530154749751091,
0.07875213027000427,
-0.08281505852937698,
-0.030479706823825836,
-0.030538149178028107,
0.06961310654878616,
0.00916... | 0.221688 |
means that label keys must only contain \_ASCII letters\_, \_numbers\_, and \_underscores\_. Label keys must also be matched by the regular expression `[a-zA-Z\_][a-zA-Z0-9\_]\*`. Any invalid characters are removed or replaced by the Grafana alerting engine before being sent to the external Alertmanager according to th... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/alert-rules/annotation-label.md | main | grafana | [
-0.12550809979438782,
0.03369386866688728,
-0.05520428344607353,
0.042291343212127686,
0.023980120196938515,
-0.025812869891524315,
0.1207972913980484,
-0.05868580937385559,
0.0800873190164566,
-0.05794869735836983,
0.04288989678025246,
-0.03230387717485428,
0.07934240251779556,
-0.0021967... | 0.175364 |
# Alert rules An alert rule is a set of evaluation criteria for when an alert rule should fire. An alert rule consists of: 1. [Queries](ref:queries-and-conditions) that select the dataset to evaluate. 1. An [alert condition](ref:alert-condition) (the threshold) that the query must meet or exceed to trigger the alert in... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/fundamentals/alert-rules/_index.md | main | grafana | [
-0.0440550222992897,
0.0401877723634243,
0.014444082044064999,
0.04430963844060898,
0.07039973139762878,
-0.11432929337024689,
0.07440628111362457,
-0.01675799861550331,
0.029135385528206825,
-0.02682904154062271,
-0.01016013789921999,
-0.07410857826471329,
0.10553358495235443,
0.031331684... | 0.188916 |
# Meta monitoring Monitor your alerting metrics to ensure you identify potential issues before they become critical. Meta monitoring is the process of monitoring your monitoring system and alerting when your monitoring is not working as it should. In order to enable you to meta monitor, Grafana provides predefined metr... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/meta-monitoring.md | main | grafana | [
-0.03916569799184799,
-0.011223233304917812,
-0.07315127551555634,
0.00902151595801115,
-0.005602617282420397,
-0.09860000014305115,
0.027135267853736877,
0.0037668468430638313,
0.0027238684706389904,
0.025883499532938004,
-0.07954266667366028,
-0.1062387004494667,
-0.0026608435437083244,
... | 0.173259 |
scheduled unless it is paused, and the value of this metric should match the total number of non-paused alert rules in Grafana. #### grafana\_alerting\_schedule\_periodic\_duration\_seconds\_bucket This metric is a histogram that shows you the time it takes to process an individual tick in the scheduler that evaluates ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/meta-monitoring.md | main | grafana | [
-0.08659739792346954,
-0.01604553498327732,
-0.09489426016807556,
0.022353312000632286,
-0.025820434093475342,
-0.055498115718364716,
0.011862833984196186,
-0.02919747866690159,
0.045700736343860626,
0.0029590672347694635,
-0.038709256798028946,
-0.08575080335140228,
0.0082396250218153,
0.... | 0.144633 |
suppressed, and unprocessed alerts in Alertmanager. Suppressed alerts are silenced alerts, and unprocessed alerts are alerts that have been sent to the Alertmanager but have not been processed. #### alertmanager\_alerts\_invalid\_total This metric is a counter that shows you the number of invalid alerts that were sent ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/meta-monitoring.md | main | grafana | [
0.013694697059690952,
-0.028503835201263428,
-0.02078319899737835,
0.08687834441661835,
0.05081361532211304,
-0.04624806344509125,
0.1205543652176857,
-0.031323421746492386,
0.115933358669281,
-0.03779279440641403,
0.04832417145371437,
-0.054955076426267624,
0.09676449745893478,
-0.0001636... | 0.212572 |
# Configure roles and permissions This guide explains how to configure roles and permissions for Grafana Alerting for Grafana OSS users. You'll learn how to manage access using roles, folder permissions, and contact point permissions. A user is any individual who can log in to Grafana. Each user is associated with a ro... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-roles/index.md | main | grafana | [
-0.07156217098236084,
-0.010457221418619156,
-0.13936883211135864,
-0.0076018632389605045,
-0.06360751390457153,
-0.04941786453127861,
0.05366038531064987,
-0.025178832933306694,
0.00169915403239429,
-0.0016798232682049274,
-0.03091057948768139,
-0.0290092620998621,
-0.0010718724224716425,
... | 0.123633 |
should have additional permissions to read users and teams. | ### Assign contact point permissions To manage contact point permissions, complete the following steps: 1. In the left-side menu, click \*\*Notification configuration\*\*, then select the \*\*Contact points\*\* tab. 1. Hover your mouse cursor over a contact ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-roles/index.md | main | grafana | [
-0.015044068917632103,
-0.027725422754883766,
-0.02364116534590721,
-0.038131993263959885,
0.06980324536561966,
-0.015903031453490257,
0.0584946870803833,
-0.03564174100756645,
0.09465206414461136,
0.006228583864867687,
-0.028303463011980057,
-0.02073623426258564,
-0.0069454326294362545,
0... | 0.048659 |
# Configure high availability Grafana Alerting uses the Prometheus model of separating the evaluation of alert rules from the delivering of notifications. In this model, the evaluation of alert rules is done in the alert generator and the delivering of notifications is done in the alert receiver. In Grafana Alerting, t... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-high-availability/_index.md | main | grafana | [
-0.07596699148416519,
0.011694148182868958,
-0.015757033601403236,
0.05374737083911896,
0.059059131890535355,
-0.12532103061676025,
-0.010288745164871216,
-0.05440853163599968,
0.02855437994003296,
0.020509453490376472,
-0.01852368749678135,
-0.04306279495358467,
0.06217145174741745,
0.014... | 0.137128 |
>}} Memberlist is the preferred option for high availability. Use Redis only in environments where direct communication between Grafana servers is not possible, such as when TCP or UDP ports are blocked. {{< /admonition >}} 1. Make sure you have a Redis server that supports pub/sub. If you use a proxy in front of your ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-high-availability/_index.md | main | grafana | [
-0.03804929181933403,
-0.10154648870229721,
-0.10409457236528397,
0.036584679037332535,
-0.01103715319186449,
-0.022508781403303146,
-0.014027209021151066,
0.007765929214656353,
-0.010890327394008636,
0.010894987732172012,
-0.045598775148391724,
-0.028763441368937492,
0.009761976078152657,
... | 0.145975 |
- \*\*Alert broadcasting:\*\* The primary instance broadcasts fired alerts to all other instances through the cluster communication channel. This ensures that every instance's embedded Alertmanager has the current alerts, which is needed for failure recovery and for the Alertmanager API to return correct data on all in... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-high-availability/_index.md | main | grafana | [
0.02486208640038967,
0.004838678520172834,
-0.0028547944966703653,
0.10564277321100235,
0.10636310279369354,
-0.03242722526192665,
0.07310003787279129,
-0.037847381085157394,
0.046683959662914276,
-0.01603037118911743,
-0.005432211793959141,
-0.014983240514993668,
0.11094970256090164,
-0.0... | 0.205694 |
provides a straightforward way to verify that your high availability configuration is working correctly. {{< admonition type="note" >}} If using a mix of `execute\_alerts=false` and `execute\_alerts=true` on the HA nodes, since the alert state is not shared amongst the Grafana instances, the instances with `execute\_al... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-high-availability/_index.md | main | grafana | [
-0.0461759977042675,
-0.008641690015792847,
-0.03356420621275902,
0.046160075813531876,
-0.0000652230010018684,
-0.09504388272762299,
0.01784789375960827,
-0.06879156827926636,
-0.0017952094785869122,
0.004750214982777834,
-0.00047379685565829277,
-0.05915309861302376,
0.01751043274998665,
... | 0.070015 |
# Performance considerations and limitations Grafana Alerting supports multi-dimensional alerting, where one alert rule can generate many alerts. For example, you can configure an alert rule to fire an alert every time the CPU of individual virtual machines max out. This topic discusses performance considerations resul... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/performance-limitations/index.md | main | grafana | [
-0.014132604002952576,
0.0010231034830212593,
-0.0875842347741127,
-0.008329496718943119,
-0.006033796817064285,
-0.11291840672492981,
0.017739474773406982,
-0.027906330302357674,
0.044941265136003494,
-0.00017214695981238037,
-0.09824229776859283,
-0.03639496862888336,
0.07236174494028091,
... | 0.110877 |
only receive Grafana managed alerts Grafana cannot be used to receive external alerts. You can only send alerts to the Grafana Alertmanager using Grafana managed alerts. You have the option to send Grafana-managed alerts to an external Alertmanager, you can find this option in the Admin tab on the Alerting page. For mo... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/performance-limitations/index.md | main | grafana | [
-0.04269622638821602,
-0.07697398215532303,
-0.06521778553724289,
0.05041654035449028,
-0.025252873077988625,
-0.13564930856227875,
-0.0014396581100299954,
-0.03531860560178757,
0.03217529132962227,
0.04319608956575394,
-0.06191857531666756,
-0.039097897708415985,
0.05006919056177139,
-0.0... | 0.054436 |
takes to write to the database periodically can be monitored using the `state\_full\_sync\_duration\_seconds` metric that is exposed by Grafana. If Grafana crashes or is force killed, then the database can be up to `state\_periodic\_save\_interval` seconds out of date. When Grafana restarts, the UI might show incorrect... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/performance-limitations/index.md | main | grafana | [
-0.05461633577942848,
-0.0625743642449379,
-0.03460082784295082,
0.021208714693784714,
0.006116467993706465,
-0.06054430454969406,
-0.05948499217629433,
-0.04519668221473694,
-0.01539217121899128,
0.05276523903012276,
-0.04878642410039902,
-0.00828952994197607,
-0.0033452711068093777,
-0.0... | 0.068773 |
# Configure alert state history Alerting can record all alert rule state changes for your Grafana managed alert rules in a Loki or Prometheus instance, or in both. - With Prometheus, you can query the `GRAFANA\_ALERTS` metric for alert state changes in \*\*Grafana Explore\*\*. - With Loki, you can query and view alert ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-alert-state-history/index.md | main | grafana | [
-0.04820060357451439,
-0.010766969993710518,
-0.03804228827357292,
0.03197791799902916,
0.014368874952197075,
-0.08720652759075165,
-0.025189099833369255,
-0.04633745923638344,
0.01860712841153145,
0.016217757016420364,
-0.041082777082920074,
-0.06124519556760788,
-0.013596330769360065,
0.... | 0.1496 |
= loki # URL of the Loki server. loki\_remote\_url = http://localhost:3100 secondaries = prometheus # Target data source UID for writing alert state changes. prometheus\_target\_datasource\_uid = ``` | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-alert-state-history/index.md | main | grafana | [
-0.07274757325649261,
0.034195899963378906,
0.014175904914736748,
0.0356532484292984,
0.052146945148706436,
-0.12417561560869217,
0.022444995120167732,
0.005491966847330332,
0.021385639905929565,
-0.0011952617205679417,
-0.013122214935719967,
-0.07716263085603714,
-0.002107897074893117,
0.... | 0.247895 |
# Provision Alerting resources Alerting infrastructure is often complex, with many pieces of the pipeline that often live in different places. Scaling this across multiple teams and organizations is an especially challenging task. Importing and exporting (or provisioning) your alerting resources in Grafana Alerting mak... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/_index.md | main | grafana | [
-0.07930155843496323,
-0.0005297324969433248,
-0.048453230410814285,
0.05593898892402649,
0.059362322092056274,
-0.0937231257557869,
0.022796982899308205,
-0.0514284148812294,
0.03687894344329834,
0.03662646934390068,
-0.05450901389122009,
-0.06892415136098862,
0.01615913026034832,
0.03194... | 0.103517 |
# Use Terraform to provision alerting resources Use Terraform’s Grafana Provider to manage your alerting resources and provision them into your Grafana system. Terraform provider support for Grafana Alerting makes it easy to create, manage, and maintain your entire Grafana Alerting stack as code. This guide outlines th... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/terraform-provisioning/index.md | main | grafana | [
-0.021610649302601814,
0.025073200464248657,
-0.046790752559900284,
0.04987586662173271,
0.05088447406888008,
-0.10383182018995285,
0.03254754841327667,
-0.05423436686396599,
0.06862907856702805,
0.056581124663352966,
-0.051258672028779984,
-0.11997433006763458,
0.06633928418159485,
0.0472... | 0.079996 |
the alert rule group in Terraform format. This exports the alert rule group as [`grafana\_rule\_group` Terraform resource](https://registry.terraform.io/providers/grafana/grafana/latest/docs/resources/rule\_group). You can edit the exported resource, or alternatively, consider creating the resource from scratch. ```ter... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/terraform-provisioning/index.md | main | grafana | [
-0.08896489441394806,
0.035376571118831635,
-0.03737325593829155,
0.06611382961273193,
0.06625860184431076,
-0.0817708745598793,
0.043496277183294296,
-0.06688857823610306,
0.07667422294616699,
0.038972701877355576,
-0.001611186657100916,
-0.10508675128221512,
0.039701852947473526,
0.01577... | 0.099029 |
### Add mute timings [Mute timings](ref:mute-timings) pause alert notifications during predetermined intervals. 1. Create or find the mute timings you want to import in Grafana. Alternatively, consider writing the resource in code as demonstrated in the example below. 1. [Export](ref:alerting\_export) the mute timing i... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/terraform-provisioning/index.md | main | grafana | [
-0.07433711737394333,
-0.0076112691313028336,
-0.00519399531185627,
0.017960598692297935,
-0.016293639317154884,
-0.036161042749881744,
0.008355679921805859,
-0.11949017643928528,
0.004916494712233543,
0.02830270677804947,
-0.04445436969399452,
-0.1386847198009491,
-0.0018614311702549458,
... | 0.029058 |
of the Terraform Alerting schemas in the [Grafana Terraform Provider documentation](https://registry.terraform.io/providers/grafana/grafana/latest/docs). - Review the [tutorial to manage a Grafana Cloud stack using Terraform](ref:provision-cloud-with-terraform). | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/terraform-provisioning/index.md | main | grafana | [
-0.03768381103873253,
-0.021383676677942276,
-0.024755913764238358,
0.03388209268450737,
-0.013124765828251839,
-0.049810923635959625,
-0.043165042996406555,
-0.0750240609049797,
0.009124889969825745,
0.09367330372333527,
-0.029225431382656097,
-0.11530506610870361,
0.030917875468730927,
0... | 0.108783 |
# Export alerting resources Export your alerting resources, such as alert rules, contact points, and notification policies for provisioning, automatically importing single folders and single groups. There are distinct methods to export your alerting resources: - [Grafana UI](#export-from-the-grafana-ui) exports in Terr... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/export-alerting-resources/index.md | main | grafana | [
-0.06641153246164322,
0.017510676756501198,
-0.07642189413309097,
0.057184670120477676,
0.07350217550992966,
-0.07303785532712936,
-0.0017816051840782166,
-0.04904377460479736,
0.03461039066314697,
0.05228695645928383,
-0.012462479993700981,
-0.07122299075126648,
-0.0129037881270051,
0.051... | 0.061742 |
using Terraform. To export your alert rule definition into Terraform (HCL) format, complete the following steps. 1. Click \*\*Alerts & IRM\*\* -> \*\*Alert rules\*\*. 2. Click \*\*Export rule definition\*\*. 3. Fill out the alert rule details. 4. Choose a provisioned folder and group to add your alert rule definition t... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/export-alerting-resources/index.md | main | grafana | [
-0.05489995703101158,
0.027938934043049812,
-0.0481860488653183,
0.0211944542825222,
0.06868430972099304,
-0.06263574957847595,
0.045514293015003204,
-0.05644899234175682,
0.05253591760993004,
0.057168398052453995,
-0.06189301609992981,
-0.13545596599578857,
0.06465936452150345,
-0.0074971... | 0.021181 |
/api/v1/provisioning/alert-rules/:uid/export | [Export an alert rule in provisioning file format](ref:export\_rule). | | Contact points | GET /api/v1/provisioning/contact-points/export | [Export all contact points in provisioning file format](ref:export\_contacts). | | Notification policy tree | GET /api/v1/provisionin... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/export-alerting-resources/index.md | main | grafana | [
-0.05738074332475662,
-0.03468118607997894,
-0.025973526760935783,
0.028488527983427048,
0.10648339241743088,
-0.0163071658462286,
0.05597984045743942,
-0.010495783761143684,
0.008308417163789272,
0.019801823422312737,
0.03643253818154335,
-0.09897817671298981,
-0.01880642957985401,
-0.024... | 0.090431 |
# Use configuration files to provision alerting resources Manage your alerting resources using configuration files that can be version controlled. When Grafana starts, it provisions the resources defined in your configuration files. [Provisioning](ref:provisioning) can create, update, or delete existing resources in yo... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md | main | grafana | [
-0.045429714024066925,
0.020283127203583717,
-0.051677387207746506,
0.031816452741622925,
0.03149052709341049,
-0.07431977987289429,
0.02134694904088974,
-0.06436064839363098,
0.042703207582235336,
0.05662298947572708,
-0.02261381410062313,
-0.06673936545848846,
0.002789613325148821,
0.031... | 0.041196 |
"NoData", "Alerting", "OK", default = NoData noDataState: Alerting # the state the alert rule will have when the query execution # failed - possible values: "Error", "Alerting", "OK" # default = Alerting execErrState: Alerting # for how long should the alert fire before alerting for: 60s # > a map of strings to pass ar... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md | main | grafana | [
-0.062994584441185,
0.048981063067913055,
-0.054345279932022095,
0.019238796085119247,
0.05448282137513161,
-0.04924517124891281,
0.06015909090638161,
-0.055577073246240616,
0.02877700701355934,
-0.02891264669597149,
-0.005958861671388149,
-0.05330386012792587,
0.04425561800599098,
-0.0044... | 0.146024 |
type: line settings: # token: xxx ``` {{< /collapse >}} {{< collapse title="MQTT" >}} #### MQTT ```yaml type: mqtt settings: # brokerUrl: tcp://127.0.0.1:1883 # clientId: grafana # topic: grafana/alerts # messageFormat: json # username: grafana # password: password1 # qos: 0 # retain: false # tlsConfig: # insecureSkipV... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md | main | grafana | [
-0.07560146600008011,
0.11362645030021667,
-0.03274965658783913,
0.03994163125753403,
-0.06971971690654755,
-0.04946945607662201,
-0.030747342854738235,
-0.019027894362807274,
0.06894856691360474,
0.021986886858940125,
-0.003579261712729931,
-0.08324012905359268,
0.05299965292215347,
0.059... | 0.020838 |
X-Grafana-Alerting-Signature-Timestamp ``` {{< /collapse >}} {{< collapse title="WeCom" >}} #### WeCom ```yaml type: wecom settings: # url: https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=xxxxxxxx # message: | {{ template "default.message" . }} # title: | {{ template "default.title" . }} ``` {{< /collapse >}} ## I... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md | main | grafana | [
-0.0972440242767334,
0.06807887554168701,
-0.05937576666474342,
0.04463977739214897,
0.016901688650250435,
-0.05622041970491409,
0.030743012204766273,
-0.021877223625779152,
0.04605725035071373,
-0.04118354618549347,
0.007377151399850845,
-0.1176803708076477,
0.021331068128347397,
0.003228... | 0.081556 |
node (allowed chars # [a-zA-Z\_:]) matchers: - alertname = Watchdog - service\_id\_X = serviceX - severity =~ "warning|critical" # a list of grafana-like matchers that an alert rule has to fulfill to match the node object\_matchers: - ['alertname', '=', 'CPUUsage'] - ['service\_id-X', '=', 'serviceX'] - ['severity', '=... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md | main | grafana | [
-0.12164013832807541,
-0.023913931101560593,
-0.020532503724098206,
0.07114174962043762,
0.0105591407045722,
-0.03785945102572441,
0.05082190781831741,
-0.034868307411670685,
0.039339400827884674,
0.017006704583764076,
-0.012586559168994427,
-0.04415655881166458,
0.05408693850040436,
-0.01... | 0.189978 |
addresses: $EMAIL ``` In this example, provisioning replaces `$EMAIL` with the value of the `EMAIL` environment variable or an empty string if it is not present. For more information, refer to [Using environment variables in the Provision documentation](ref:provisioning\_env\_vars). In alerting resources, most properti... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/provision-alerting-resources/file-provisioning/index.md | main | grafana | [
0.02707180753350258,
0.025492938235402107,
0.05017555132508278,
0.05836882069706917,
0.08184512704610825,
-0.01139160804450512,
0.09721338748931885,
-0.024527907371520996,
0.0671016126871109,
-0.0015667214756831527,
-0.001990554854273796,
-0.10596885532140732,
0.02510826662182808,
0.011565... | 0.052389 |
# Configure RBAC [Role-based access control (RBAC)](/docs/grafana/latest/administration/roles-and-permissions/access-control/plan-rbac-rollout-strategy/) for Grafana Enterprise and Grafana Cloud provides a standardized way of granting, changing, and revoking access, so that users can view and modify Grafana resources. ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-rbac/_index.md | main | grafana | [
-0.07847518473863602,
-0.0009083729237318039,
-0.10851816087961197,
0.031974490731954575,
-0.10120610892772675,
-0.00036295418976806104,
0.04139750078320503,
-0.051191654056310654,
-0.02123362384736538,
0.05711310729384422,
-0.0576813668012619,
0.011331773363053799,
0.02406030148267746,
0.... | 0.112221 |
alert rules in external data sources that support alerting. | Action | Applicable scope | Description | | ---------------------------- | -------------------------------------- | ---------------------------------------------------------------------------------------------- | | `alert.rules.external:read` | `datasources:... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-rbac/_index.md | main | grafana | [
-0.06080920994281769,
0.012905756011605263,
-0.05667300522327423,
0.04553651809692383,
0.0621744841337204,
-0.14450287818908691,
0.10492656379938126,
0.04702082276344299,
0.001559558673761785,
0.0006811575731262565,
0.015168311074376106,
-0.05974167212843895,
0.062241584062576294,
-0.06621... | 0.12398 |
for managing notification templates. | Action | Applicable scope | Description | | ------------------------------------------ | ---------------- | ------------------------------------------------------------------------------- | | `alert.notifications.templates:read` | n/a | Read templates. | | `alert.notifications.tem... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-rbac/_index.md | main | grafana | [
-0.02365199290215969,
0.022886257618665695,
-0.022875448688864708,
0.08420650660991669,
0.03408472612500191,
-0.021649610251188278,
0.07524906098842621,
0.011474915780127048,
0.0396573506295681,
0.035789407789707184,
-0.016400111839175224,
-0.057111114263534546,
0.022496899589896202,
0.008... | 0.128914 |
# Manage access using roles In Grafana Enterprise and Grafana Cloud there are Basic, Fixed, and Custom roles. ## Basic roles There are four basic roles: `Admin`, `Editor`, `Viewer`, and `None`. Each basic role contains a number of fixed roles. Details of the basic roles and the access they provide for Grafana Alerting ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-rbac/access-roles/index.md | main | grafana | [
-0.021613309159874916,
0.022318195551633835,
-0.09047873318195343,
0.01529289036989212,
-0.06935504823923111,
-0.014293525367975235,
0.00922437384724617,
-0.0409541018307209,
0.008031376637518406,
0.028769319877028465,
-0.01956867426633835,
-0.044353824108839035,
0.026191899552941322,
-0.0... | 0.080027 |
provisioning API: `fixed:alerting.provisioning:writer` | `alert.provisioning:read` and `alert.provisioning:write` | Manage all alert rules, notification policies, contact points, templates, in the organization using the provisioning API. | | Set provisioning status: `fixed:alerting.provisioning.provenance:writer` | `al... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-rbac/access-roles/index.md | main | grafana | [
-0.06313751637935638,
-0.0479830838739872,
-0.047301970422267914,
0.061200208961963654,
0.0753469169139862,
-0.07503385841846466,
0.11992055177688599,
-0.013601342216134071,
0.005150024313479662,
0.03875233605504036,
0.0024655687157064676,
-0.038645897060632706,
0.04858919605612755,
0.1053... | 0.092554 |
custom role for write access to alert rules that uses simplified routing: ``` PUT access-control/roles { "name": "custom:alert\_rules\_updater", "displayName": "Alert rules editor in folder F", "description": "Edit access to rules in folder F that use DS1 and DS2", "permissions": [ { "action": "alert.rules:read", "scop... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-rbac/access-roles/index.md | main | grafana | [
-0.005952303297817707,
0.0009061734890565276,
-0.05863802507519722,
0.09768009185791016,
0.023551562801003456,
-0.057902973145246506,
0.09739336371421814,
0.025678766891360283,
0.024449650198221207,
0.008570956997573376,
-0.019025281071662903,
-0.008113387040793896,
0.025180421769618988,
0... | 0.073831 |
# Manage access using folders or data sources You can extend the access provided by a role to alert rules and rule-specific silences by assigning permissions to individual folders or data sources. {{< admonition type="note" >}} Data source query permissions are required to create an alert rule or modify an alert rule's... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-rbac/access-folders/index.md | main | grafana | [
0.013543867506086826,
0.05871639773249626,
-0.06334378570318222,
0.07336867600679398,
0.07932727783918381,
-0.05786474421620369,
0.13083122670650482,
-0.053940627723932266,
0.059900570660829544,
-0.056667979806661606,
0.008443423546850681,
-0.027758533135056496,
0.042767129838466644,
-0.02... | 0.086115 |
# Configure Alertmanagers Grafana Alerting is based on the architecture of the Prometheus alerting system. Grafana sends firing and resolved alerts to an Alertmanager, which is responsible for [handling notifications](ref:notifications). This architecture decouples alert rule evaluation from notification handling, impr... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-alertmanager/_index.md | main | grafana | [
-0.08511586487293243,
0.02992948703467846,
-0.04065486416220665,
0.03736923635005951,
0.04018693044781685,
-0.11089663952589035,
0.04544646292924881,
-0.04735284671187401,
0.03464975208044052,
0.00827860552817583,
-0.019757842645049095,
-0.08067969977855682,
0.035370130091905594,
0.0786332... | 0.145656 |
Alertmanager, click the \*\*Enable/Disable\*\* button to toggle receiving Grafana-managed alerts. When activated, the Alertmanager displays `Receiving Grafana-managed alerts`. {{< figure src="/media/docs/alerting/grafana-alerting-settings.png" max-width="750px" alt="Grafana Alerting Settings page" >}} All Grafana-manag... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/set-up/configure-alertmanager/_index.md | main | grafana | [
-0.018684502691030502,
-0.0007097751367837191,
-0.04238175228238106,
0.05991404503583908,
0.060373030602931976,
-0.08176718652248383,
-0.002967739710584283,
-0.09791038185358047,
0.023450490087270737,
0.06836821883916855,
0.014681297354400158,
-0.044685084372758865,
0.02887897752225399,
0.... | 0.074344 |
# Create and link alert rules to panels Grafana allows you to link an alert rule to a dashboard panel. This can help you: - Inform alert responders about where to investigate and which data to examine. - Visualize the alert state directly from dashboards. - Include a screenshot of the panel in notification messages. An... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/link-alert-rules-to-panels.md | main | grafana | [
-0.07726237177848816,
0.008345024660229683,
-0.045294687151908875,
0.026502104476094246,
0.10442069917917252,
-0.010395976714789867,
0.08160048723220825,
-0.006678488105535507,
0.04724288359284401,
0.0033226676750928164,
-0.03291955590248108,
-0.08919833600521088,
0.07492686808109283,
0.05... | 0.080206 |
# Configure Grafana-managed alert rules Grafana-managed alert rules are the default way to create alert rules in Grafana. Grafana-managed rules inherit their model from Prometheus Alerting and extend it with greater flexibility—such as multi-data source queries, expression-based transformations, advanced alert conditio... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/create-grafana-managed-rule.md | main | grafana | [
-0.07862498611211777,
-0.00810453575104475,
-0.05485258623957634,
0.05280639976263046,
0.025491386651992798,
-0.10011347383260727,
0.047286782413721085,
-0.045616038143634796,
-0.006924829911440611,
0.005373802501708269,
0.005194243974983692,
-0.05203567445278168,
0.062465544790029526,
0.0... | 0.115483 |
\*\*Options\*\* drop-down menu, specify a [time range](ref:time-units-and-relative-ranges). Note that Grafana Alerting only supports fixed relative time ranges, for example, `now-24hr: now`. It doesn't support absolute time ranges: `2021-12-02 00:00:00 to 2021-12-05 23:59:592` or semi-relative time ranges: `now/d to: n... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/create-grafana-managed-rule.md | main | grafana | [
-0.06521794945001602,
0.029228687286376953,
-0.040064260363578796,
0.06678591668605804,
0.03348959609866142,
-0.037065599113702774,
0.0092390738427639,
-0.04137890785932541,
0.040174901485443115,
0.01709386706352234,
-0.01396991778165102,
-0.12514851987361908,
0.03397615626454353,
0.021130... | 0.058205 |
a "Recovering" state for the duration of time set here. The Recovering state can be used to reduce noise from flapping alerts. Select "none" stop an alert from firing immediately after the breach threshold is cleared. 1. Turn on pause alert notifications, if required. You can pause alert rule evaluation to prevent nois... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/create-grafana-managed-rule.md | main | grafana | [
-0.017120514065027237,
0.040147822350263596,
0.01610707677900791,
0.0989518091082573,
0.0927964523434639,
-0.04133637994527817,
0.07906107604503632,
-0.08360625058412552,
0.101277656853199,
0.00008170657383743674,
0.004106136504560709,
-0.03102194145321846,
0.060588039457798004,
-0.0799035... | 0.082157 |
# Configure data source-managed alert rules Data source-managed alert rules are alert rules that are stored in the data source, such as in Prometheus or Loki, rather than in Grafana. In Grafana Alerting, you can: 1. Create and edit data source-managed rules for Grafana Mimir and Grafana Loki data sources. 1. View rules... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/create-data-source-managed-rule.md | main | grafana | [
-0.10036769509315491,
0.003942884039133787,
-0.06249091029167175,
0.04027988761663437,
0.014140349812805653,
-0.1278488039970398,
0.011052122339606285,
-0.061743274331092834,
-0.023644573986530304,
0.03305583819746971,
-0.009118232876062393,
-0.06240123137831688,
0.03589072450995445,
0.032... | 0.112299 |
do not want to manage alert rules for a particular data source, go to its settings and clear the \*\*Manage alerts via Alerting UI\*\* checkbox. #### Provisioning Note that if you delete an alert resource created in the UI, you can no longer retrieve it. To backup and manage alert rules, you can [provision alerting res... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/create-data-source-managed-rule.md | main | grafana | [
-0.027067529037594795,
0.06737903505563736,
-0.01736249215900898,
0.05442548915743828,
0.10450588166713715,
-0.0890541672706604,
0.040692318230867386,
-0.10604269802570343,
0.039866115897893906,
0.05365024134516716,
-0.0451299287378788,
-0.0505872517824173,
0.06103719770908356,
-0.01177873... | 0.007576 |
rule\*\*. [//]: <> ({{< docs/shared lookup="alerts/configure-notification-message.md" source="grafana" version="" >}}) | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/create-data-source-managed-rule.md | main | grafana | [
-0.05124901235103607,
0.09817271679639816,
0.03604822978377342,
0.022219449281692505,
0.1115693598985672,
-0.032800327986478806,
0.038085103034973145,
-0.08909867703914642,
0.07837142795324326,
0.003517287317663431,
-0.05127040669322014,
-0.019697297364473343,
0.034487999975681305,
0.00750... | 0.078046 |
# Import data source-managed rules to Grafana-managed rules You can convert existing alert rules from data sources such as Mimir, Loki, and Prometheus into Grafana-managed alert rules. This enables you to operate and manage these rules using Grafana Alerting. This guide explains two methods for importing data source-ma... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/alerting-migration.md | main | grafana | [
-0.08064506202936172,
-0.048652686178684235,
-0.07200181484222412,
-0.0052129789255559444,
0.04253054037690163,
-0.1388496607542038,
0.002366533735767007,
-0.05588585138320923,
-0.03387904912233353,
0.03201177343726158,
0.031889934092760086,
-0.04454587772488594,
0.07090684026479721,
0.005... | 0.116733 |
- \*\*Folders\*\*: `Creator`. The Folders permission is optional and only necessary if you want to create new folders for your target namespace. If your account doesn't have permissions to view a namespace, the tool creates a new one. To convert data source-managed alert rules to Grafana managed alerts: 1. Go to \*\*Al... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/alerting-migration.md | main | grafana | [
-0.0964009165763855,
-0.03956978768110275,
-0.09358637034893036,
0.030421458184719086,
0.026910169050097466,
-0.12683556973934174,
0.0008397171040996909,
-0.06895110756158829,
-0.0017349814297631383,
0.038422245532274246,
0.021756427362561226,
-0.1082443818449974,
0.06651418656110764,
0.00... | 0.106416 |
that: 1. When using the `/api/convert/` endpoint, `mimirtool` interacts with Grafana—not with a Mimir instance. In this case, `MIMIR\_TENANT\_ID` must always be set to `1`. 1. The [`X-Grafana-Alerting-Datasource-UID` header](#x-grafana-alerting-datasource-uid) configures the data source that the imported alert rules wi... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/alerting-migration.md | main | grafana | [
-0.08303429931402206,
-0.0068535227328538895,
-0.07827497273683548,
0.02087240479886532,
-0.008159702643752098,
-0.1163516491651535,
-0.019987953826785088,
-0.06591122597455978,
0.01603899709880352,
0.009001003578305244,
0.02257661148905754,
-0.11966313421726227,
0.04804976284503937,
0.004... | 0.018546 |
less than `group\_interval`. | | `mute\_time\_intervals` | `[]string` | No | `["maintenance"]` | One or more mute time interval names that silence alerts during those windows. | | `active\_time\_intervals` | `[]string` | No | `["maintenance"]` | List of active time interval names. Alerts are suppressed unless the curre... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/alerting-migration.md | main | grafana | [
-0.13163504004478455,
0.011041558347642422,
-0.0745069682598114,
0.016314681619405746,
-0.025852413848042488,
-0.0847020149230957,
-0.02026595175266266,
-0.027885649353265762,
0.0382935032248497,
-0.02355065941810608,
0.008405143395066261,
-0.0727119967341423,
0.02101045288145542,
0.013889... | 0.226723 |
# Configure alert rules [Alert rules](ref:alert-rules) are the central component of your alerting system. An alert rule consists of one or more queries and expressions that select the data you want to measure. It contains a condition to trigger the alert, an evaluation period that determines how often the rule is evalu... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/_index.md | main | grafana | [
-0.08124719560146332,
0.015958765521645546,
-0.05028176307678223,
0.05188523605465889,
0.017936693504452705,
-0.13047382235527039,
0.051589515060186386,
-0.032477967441082,
0.009255880489945412,
0.0031348506454378366,
-0.03483397513628006,
-0.09131193161010742,
0.05133039131760597,
0.02222... | 0.171506 |
# Create data source-managed recording rules [Recording rules](ref:create-recording-rules) allow you to periodically pre-compute frequently used or computationally expensive queries, saving the results as a new time series metric. Alert rules and dashboards can then query the new metric resulting from the recording rul... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/create-recording-rules/create-data-source-managed-recording-rules.md | main | grafana | [
-0.08487801998853683,
-0.009898750111460686,
-0.034898970276117325,
0.03384385257959366,
0.05339600145816803,
-0.14618928730487823,
0.01851077564060688,
-0.02533809281885624,
0.006886153947561979,
-0.005218398291617632,
0.011157403700053692,
-0.05957067385315895,
0.0406084805727005,
0.0312... | 0.175259 |
# Migrate recorded queries Users can transpose their [now-depreciated recorded queries](/docs/grafana/latest/administration/recorded-queries/) into Grafana-managed recording rules in a few easy steps. The query PromQL for each recorded query has been exposed on the recorded queries list along with the existing datasour... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/create-recording-rules/migrate-recorded-queries.md | main | grafana | [
-0.08312872052192688,
0.00004252812505001202,
-0.06224668398499489,
0.057200413197278976,
-0.04047215357422829,
-0.0709238201379776,
0.02716706693172455,
-0.04349202662706375,
-0.015198842622339725,
0.039302024990320206,
-0.03738979622721672,
-0.07066112756729126,
0.0592084638774395,
-0.00... | 0.070477 |
# Create Grafana-managed recording rules for Tempo {{< docs/private-preview product="Grafana-managed recording rules for Tempo" >}} Grafana-managed recording rules let you pre-compute query results and store them as new time series metrics. These metrics can then be reused in dashboards, alerts, or downstream queries, ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/create-recording-rules/create-recording-rule-tempo.md | main | grafana | [
-0.10982030630111694,
-0.020429858937859535,
-0.11895673722028732,
0.041838500648736954,
-0.03516790270805359,
-0.01292997132986784,
0.0191851444542408,
-0.043314557522535324,
0.014665109105408192,
-0.02038956992328167,
-0.037936363369226456,
-0.08753606677055359,
0.01231896411627531,
-0.0... | 0.12344 |
can apply the `offset` modifier in your Prometheus queries. | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/create-recording-rules/create-recording-rule-tempo.md | main | grafana | [
-0.08397389948368073,
0.06109501048922539,
0.012165973894298077,
0.011708072386682034,
-0.00640872260555625,
-0.1052761822938919,
0.013517276383936405,
-0.013139141723513603,
-0.026770099997520447,
-0.024702996015548706,
0.05317002162337303,
-0.04646291956305504,
0.01500086858868599,
-0.06... | 0.169465 |
# Configure recording rules Recording rules allows you to periodically pre-compute frequently used or computationally expensive queries, saving the results as a new time series metric. For instance, you can create a recording rule generating a new metric, `error\_9001\_count`, which counts occurrences of a specific log... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/create-recording-rules/_index.md | main | grafana | [
-0.03936298191547394,
0.02410122938454151,
-0.07058724761009216,
0.053210992366075516,
0.05515417456626892,
-0.040841370820999146,
0.08528365939855576,
0.03243172541260719,
0.06004701554775238,
-0.03827255964279175,
-0.050704751163721085,
-0.043200571089982986,
0.09325676411390305,
0.00246... | 0.190194 |
# Create Grafana-managed recording rules [Recording rules](ref:create-recording-rules) allow you to periodically pre-compute frequently used or computationally expensive queries, saving the results as a new time series metric. Alert rules and dashboards can then query the new metric resulting from the recording rule. T... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/create-recording-rules/create-grafana-managed-recording-rules.md | main | grafana | [
-0.12428721785545349,
0.017833858728408813,
-0.09526872634887695,
0.027371933683753014,
0.0037228695582598448,
-0.09939698874950409,
-0.0015992008848115802,
-0.029719889163970947,
0.01964246667921543,
0.016849737614393234,
-0.04860841855406761,
-0.04839959368109703,
0.014627443626523018,
0... | 0.144731 |
you don't need to add additional expressions. b. Click \*\*Preview\*\* to verify that the expression is successful. 1. Click \*\*Set as recording rule output\*\* on the query or expression you want to set as your rule output. ## Set evaluation behavior Use recording rule evaluation to determine how frequently a recordi... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/create-recording-rules/create-grafana-managed-recording-rules.md | main | grafana | [
-0.03851139172911644,
0.03793029859662056,
-0.07985378056764603,
0.05617179721593857,
0.018863363191485405,
0.06787355989217758,
0.05749831721186638,
-0.0087179746478796,
-0.016249263659119606,
-0.000966974999755621,
0.00350276124663651,
-0.12396825104951859,
0.09147457778453827,
-0.020964... | 0.011518 |
# Alerting template language Notification templates and alert rule templates, such as annotations and labels, both use the Go template language, [text/template](https://pkg.go.dev/text/template). Both types of templates can use the same keywords, functions, and comparison operators of the Go template language, such as ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/templates/language.md | main | grafana | [
0.022681131958961487,
0.08483906090259552,
-0.010744140483438969,
-0.017379695549607277,
0.0945073813199997,
0.06658454239368439,
0.13102053105831146,
0.018773969262838364,
0.05929313972592354,
-0.11021681874990463,
0.012797519564628601,
-0.01835966296494007,
-0.00830901600420475,
0.086860... | 0.10331 |
# Labels and annotations template examples Templating allows you to add dynamic data from queries to alert labels and annotations. Dynamic data enhances alert context, making it easier for responders to quickly assess and address the issue. This page provides common examples for templating labels and annotations. For m... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/templates/examples.md | main | grafana | [
-0.012394257821142673,
0.1292189359664917,
-0.04821956530213356,
0.10702414065599442,
0.12491641938686371,
0.05226628854870796,
0.15551245212554932,
0.03494124487042427,
0.09238504618406296,
-0.07740616798400879,
-0.055669624358415604,
-0.07075360417366028,
0.008531196974217892,
-0.0049226... | 0.243945 |
-}}critical {{- else if (gt $values.A.Value 80.0) -}}high {{- else if (gt $values.A.Value 60.0) -}}medium {{- else -}}low {{- end -}} ``` In this example, the `severity` label is determined by the query value: - `critical` for values above 90, - `high` for values above 80, - `medium` for values above 60, - and `low` fo... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/templates/examples.md | main | grafana | [
0.009667552076280117,
0.10132166743278503,
-0.05250507965683937,
0.06769663840532303,
0.004711086396127939,
0.03424559906125069,
0.138534814119339,
0.031091203913092613,
0.049447715282440186,
-0.05138340964913368,
0.0020321800839155912,
-0.08956793695688248,
0.05540396273136139,
0.01178022... | 0.101554 |
(match "B[0-9]+" $k) -}} {{ $k }}: {{ $v.Labels }}{{ end }} {{ end }} ``` For example, a classic condition for two time series exceeding a single condition would print: ``` B0: instance=server1 B1: instance=server2 ``` If the classic condition has two or more conditions, and a time series exceeds multiple conditions at... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/templates/examples.md | main | grafana | [
-0.00010327019117539749,
0.09397650510072708,
-0.012523068115115166,
-0.019149020314216614,
0.03386744484305382,
0.037161387503147125,
0.08507754653692245,
-0.10414369404315948,
0.051353819668293,
-0.0332353375852108,
0.017884818837046623,
-0.07160595804452896,
0.014231369830667973,
0.0106... | 0.011254 |
# Annotation and label template reference Annotations and labels in alert rules can be defined using plain text. However, you can also define templates to customize their values with dynamic data from alert rule queries. For example, you can template the `summary` annotation to include information from query values, pr... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/templates/reference.md | main | grafana | [
-0.005300134886056185,
0.10997645556926727,
-0.04757034033536911,
0.08728832751512527,
0.06913840025663376,
0.056709662079811096,
0.16104741394519806,
0.03913598880171776,
0.07635172456502914,
-0.06731908023357391,
-0.03398342430591583,
-0.043222006410360336,
0.04186875373125076,
0.0079269... | 0.115968 |
Float | The value returned by the instant query or expression. | | `Labels` | Key/value pairs | The labels associated with the instance query or expression. | Here's the previous example printing now the value of the instant query with Ref ID `A`: ``` {{ $values.A.Value }} CPU usage for {{ $labels.instance }} over the ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/templates/reference.md | main | grafana | [
-0.008412177674472332,
0.12647686898708344,
-0.0578715018928051,
0.1294836699962616,
0.0214033555239439,
0.01458651851862669,
0.09089964628219604,
0.010084642097353935,
0.06360846012830734,
-0.015334195457398891,
-0.02186470665037632,
-0.06571564078330994,
-0.020228497684001923,
-0.0370229... | 0.060168 |
Converts a Unix timestamp in seconds to time. | \*\*Strings\*\* | Name | Arguments | Returns | Description | | ------------------------------- | -------------------------- | ------- | --------------------------------------------------------------------------------------------- | | [title](#title) | string | string | Ca... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/templates/reference.md | main | grafana | [
0.043436549603939056,
0.11613411456346512,
-0.03327831253409386,
-0.00544969504699111,
-0.02477308176457882,
-0.01124706119298935,
0.004943751264363527,
0.06849436461925507,
-0.018858926370739937,
-0.027745230123400688,
0.028818612918257713,
-0.05782566964626312,
0.052012696862220764,
-0.0... | 0.054349 |
"example.com:8080" }} ``` ``` example.com ``` #### match The `match` function matches the text against a regular expression pattern: ``` {{ match "a.\*" "abc" }} ``` ``` true ``` #### reReplaceAll The `reReplaceAll` function replaces text matching the regular expression: ``` {{ reReplaceAll "localhost:(.\*)" "example.c... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/templates/reference.md | main | grafana | [
-0.08327046781778336,
0.0666544958949089,
0.14360404014587402,
0.04636172205209732,
-0.007819785736501217,
-0.045771997421979904,
-0.003530851099640131,
-0.03039947897195816,
-0.03129734471440315,
0.042350102216005325,
0.025502583011984825,
-0.006972093600779772,
0.034449029713869095,
0.02... | -0.035185 |
# Template annotations and labels You can use templates to customize alert and notification messages, including dynamic data from alert rule queries. In Grafana Alerting, you can template alert messages in two ways. 1. \*\*Template annotations and labels\*\*: In the alert rule definition, you can template annotations a... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/templates/_index.md | main | grafana | [
-0.037754401564598083,
0.08952051401138306,
0.022083237767219543,
0.05511690676212311,
0.04929269105195999,
0.03410559520125389,
0.09907858818769455,
0.03661733493208885,
0.078119195997715,
-0.042153745889663696,
-0.05177898332476616,
-0.027630722150206566,
0.05307232588529587,
0.031370893... | 0.152969 |
annotation field (`summary`, `description`, `runbook\_url`, `custom`). ### Preview annotation templates You can template annotations when creating or editing an alert rule. {{< figure src="/media/docs/alerting/alert-rule-using-annotation-template.png" max-width="1200px" alt="An alert rule templating the annotation summ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/templates/_index.md | main | grafana | [
-0.07083748281002045,
0.05058752000331879,
-0.019406793639063835,
0.03643491491675377,
0.08141706138849258,
0.004104457329958677,
0.03694616258144379,
-0.003526115557178855,
0.08414103090763092,
-0.017029738053679466,
-0.05653202533721924,
-0.061921119689941406,
0.0247051939368248,
0.02361... | 0.152872 |
practical example of templating, refer to our [Getting Started with Templating tutorial](https://grafana.com/tutorials/alerting-get-started-pt4/). {{< /admonition >}} | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/alerting-rules/templates/_index.md | main | grafana | [
-0.0410650335252285,
0.11803550273180008,
-0.041261982172727585,
0.06287247687578201,
0.0504009909927845,
-0.027824878692626953,
0.026584263890981674,
0.02514740824699402,
0.06567953526973724,
-0.034161701798439026,
0.01773739606142044,
-0.011903814971446991,
-0.022054672241210938,
0.02942... | 0.203888 |
# Alerting best practices Designing and configuring an effective alerting system takes time. This guide focuses on building alerting systems that scale with real-world operations. The practices described here are intentionally high-level and apply regardless of tooling. Whether you use Prometheus, Grafana Alerting, or ... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/guides/best-practices.md | main | grafana | [
-0.0182641614228487,
-0.012254852801561356,
0.05197938159108162,
0.03374022617936134,
0.06953336298465729,
-0.11931078135967255,
0.028610710054636,
0.00237917248159647,
0.05625379458069801,
0.0032310490496456623,
-0.060224149376153946,
-0.0020061018876731396,
0.014852178283035755,
0.049269... | 0.204673 |
the alert. Anyone on call should be able to understand what's wrong and what to do next without deep knowledge of the system or alert configuration. Avoid vague alerts that force responders to spend time figuring out context. Every alert should clearly explain why it exists, what triggered it, and how to investigate. U... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/guides/best-practices.md | main | grafana | [
-0.010508735664188862,
0.019604045897722244,
-0.03196635842323303,
0.03668848052620888,
0.05904180929064751,
-0.07455424964427948,
0.09346242994070053,
0.042107291519641876,
0.08243526518344879,
-0.025942623615264893,
-0.05147683247923851,
-0.0044738226570189,
0.015043926425278187,
0.01783... | 0.158124 |
threshold for some minutes. Also, stabilize alerts by tuning query ranges and aggregations. Using raw data makes alerts sensitive to noise. Instead, evaluate over a time window and aggregate the data to smooth short spikes. ```promql # Reacts to transient spikes. Avoid this. cpu\_usage > 90 # Smooth fluctuations. avg\_... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/guides/best-practices.md | main | grafana | [
-0.025125466287136078,
0.020631279796361923,
-0.014577634632587433,
0.10244745761156082,
0.03953882306814194,
-0.1410951167345047,
0.08696508407592773,
0.050512392073869705,
0.06338182091712952,
-0.03585471212863922,
-0.03418935462832451,
0.0012174873845651746,
0.020725617185235023,
-0.005... | 0.167824 |
# Handle missing data in Grafana Alerting Missing data from when a target stops reporting metric data can be one of the most common issues when troubleshooting alerts. In cloud-native environments, this happens all the time. Pods or nodes scale down to match demand, or an entire job quietly disappears. When this happen... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/guides/missing-data.md | main | grafana | [
-0.03080049529671669,
-0.007408882956951857,
0.021422095596790314,
0.08067085593938828,
0.04595639929175377,
-0.1088106706738472,
-0.048224691301584244,
-0.07514986395835876,
0.061021123081445694,
0.05401933565735817,
-0.02079056389629841,
-0.06801297515630722,
0.007350257597863674,
-0.025... | 0.091872 |
doesn't fire alerts when the query returns no data. It simply assumes there was nothing to report, like with query errors. Missing data won’t trigger existing alerts unless you explicitly check for it. In Prometheus, a common way to catch missing data is by to use the `absent\_over\_time` function. `absent\_over\_time(... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/guides/missing-data.md | main | grafana | [
0.007294369395822287,
0.02586900070309639,
-0.015936484560370445,
0.0871753990650177,
0.07998831570148468,
-0.08598394691944122,
0.0222138874232769,
-0.05234205350279808,
0.07902508229017258,
-0.06937272846698761,
0.020236169919371605,
-0.08276532590389252,
0.029800089076161385,
-0.0336613... | 0.104638 |
eviction process. Here’s what happens under the hood: - Alert instances with missing data keep their last state for two evaluation intervals. - If the data is still missing after that: - Grafana adds the annotation `grafana\_state\_reason: MissingSeries`. - The alert instance transitions to the `Normal` state. - A \*\*... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/guides/missing-data.md | main | grafana | [
-0.0837194174528122,
0.027369022369384766,
-0.019043806940317154,
0.09315688908100128,
0.03480011224746704,
-0.06879922747612,
-0.0038545720744878054,
-0.09939681738615036,
0.1422806829214096,
-0.0358351431787014,
0.009322636760771275,
-0.038009464740753174,
-0.015137465670704842,
-0.04650... | 0.104891 |
alert rule then triggers an alert instance for each missing region. You can apply the same technique to any label or target dimension. ## Conclusion Missing data isn’t always a failure. It’s a common scenario in dynamic environments when certain targets stop reporting. Grafana Alerting handles distinct scenarios automa... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/guides/missing-data.md | main | grafana | [
-0.014496589079499245,
0.028645381331443787,
-0.009575769305229187,
0.062358010560274124,
0.026034018024802208,
-0.08474373072385788,
0.0366089828312397,
-0.07803961634635925,
0.03124150075018406,
-0.041348524391651154,
0.018795371055603027,
-0.133726105093956,
0.04935423657298088,
-0.0423... | 0.107366 |
# Handle connectivity errors in alerts Connectivity issues are a common cause of misleading alerts or unnoticed failures. There could be a number of reasons for these errors. Maybe your target went offline, or Prometheus couldn't scrape it. Or maybe your alert query failed because its target timed out or the network we... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/guides/connectivity-errors.md | main | grafana | [
-0.028655624017119408,
0.018718361854553223,
0.020441684871912003,
0.057822685688734055,
0.03779466450214386,
-0.1264469027519226,
0.049055084586143494,
-0.019999312236905098,
0.024432770907878876,
-0.007240355480462313,
-0.03190639987587929,
-0.01841195672750473,
0.04442035034298897,
0.01... | 0.133694 |
However, this kind of `up` alert has a few potential downfalls: - \*\*Failures can slip between scrape intervals\*\*: An outage that starts and ends between two evaluations go undetected. You could shorten the `for` duration, but this might lead to scrape failures that trigger false alarms. - \*\*Intermittent recoverie... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/guides/connectivity-errors.md | main | grafana | [
-0.08887411653995514,
0.04943813011050224,
-0.018201341852545738,
0.07923906296491623,
0.06658950448036194,
-0.11324440687894821,
0.042760226875543594,
-0.010553810745477676,
0.04789462313055992,
-0.06371433287858963,
0.004567589145153761,
0.030484436079859734,
0.03747285157442093,
-0.0574... | 0.082688 |
internal scrape fails or the service is externally unreachable. `up == 0 or probe\_success == 0` As with the `up` metric, you might want to smooth this out using `avg\_over\_time()` for more robust detection. The smooth version might look like: `avg\_over\_time(up[10m]) < 0.8 or avg\_over\_time(probe\_success[10m]) < 0... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/guides/connectivity-errors.md | main | grafana | [
-0.07605071365833282,
-0.00009523928019916639,
0.007388158235698938,
0.05286947265267372,
0.05233693867921829,
-0.19636447727680206,
0.024443382397294044,
-0.03576338663697243,
0.0068621644750237465,
-0.016675177961587906,
-0.01784587651491165,
-0.05784062668681145,
0.024911098182201385,
-... | 0.135901 |
other alerts detecting connectivity issues. - \*\*Keep Last State\*\*: Keeps the previous state until the query succeeds again. Suitable for unstable environments to avoid flapping alerts. {{< figure src="/media/docs/alerting/alert-rule-configure-no-data-and-error-v2.png" alt="A screenshot of the `Configure error handl... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/guides/connectivity-errors.md | main | grafana | [
-0.02226673811674118,
0.039075497537851334,
0.005379252135753632,
0.07518512010574341,
0.03205140680074692,
-0.137661874294281,
0.04131226986646652,
-0.022249622270464897,
0.0032377506140619516,
0.0002547719341237098,
-0.022221757099032402,
-0.0156392902135849,
0.0847838744521141,
0.037321... | 0.098369 |
# Example of dynamic labels in alert instances Labels are essential for scaling your alerting setup. They define metadata like `severity`, `team`, `category`, or `environment`, which you can use for alert routing. A label like `severity="critical"` can be set statically in the alert rule configuration, or dynamically b... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/examples/dynamic-labels.md | main | grafana | [
-0.05480274185538292,
0.027946624904870987,
-0.08726111054420471,
0.061637744307518005,
-0.05225559324026108,
-0.029321160167455673,
0.08643944561481476,
0.019428987056016922,
0.05720251053571701,
-0.07363713532686234,
-0.04031631350517273,
-0.06138879433274269,
0.0336746908724308,
0.03227... | 0.127881 |
You can define a single rule and assign `severity` dynamically using a template: ```go {{/\* $values.B.Value refers to the numeric result from query B \*/}} {{- if gt $values.B.Value 90.0 -}}critical {{- else if gt $values.B.Value 80.0 -}}warning {{- else if gt $values.B.Value 70.0 -}}minor {{- else -}}none {{- end -}}... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/examples/dynamic-labels.md | main | grafana | [
0.023806946352124214,
0.0688927099108696,
-0.01648719795048237,
0.047726184129714966,
0.032676294445991516,
0.030624283477663994,
0.1185062825679779,
0.03886204585433006,
0.03217250108718872,
-0.034821320325136185,
-0.02296377718448639,
-0.09570182859897614,
0.07611222565174103,
0.08272650... | 0.042999 |
it with TestData You can replicate this scenario using the [TestData data source](ref:testdata-data-source) to simulate an unstable signal—like monitoring a noisy sensor. This setup reproduces label flapping and shows how dynamic label values affect alert instance behavior. 1. Add the \*\*TestData\*\* data source throu... | https://github.com/grafana/grafana/blob/main//docs/sources/alerting/examples/dynamic-labels.md | main | grafana | [
-0.060362908989191055,
-0.023135149851441383,
-0.01920066401362419,
0.08424216508865356,
0.03855476900935173,
-0.052312202751636505,
0.15944847464561462,
-0.06839007884263992,
0.09116845577955246,
-0.08070208877325058,
-0.05044079199433327,
-0.021416353061795235,
0.06013372540473938,
-0.02... | 0.11919 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.