Update dependency prettier to v3.6.2 (#108689)

* Update dependency prettier to v3.6.2

* run prettier

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Ashley Harrison <ashley.harrison@grafana.com>
This commit is contained in:
renovate[bot]
2025-07-25 17:47:44 +01:00
committed by GitHub
parent 20cea80795
commit c94f930950
104 changed files with 50 additions and 250 deletions
@@ -233,7 +233,6 @@ This setup reproduces label flapping and shows how dynamic label values affect a
1. Simulate a query (`$A`) that returns a noisy signal.
Select **TestData** as the data source and configure the scenario.
- Scenario: Random Walk
- Series count: 1
- Start value: 51
@@ -241,7 +240,6 @@ This setup reproduces label flapping and shows how dynamic label values affect a
- Spread: 100 (ensures large changes between consecutive data points)
1. Add an expression.
- Type: Reduce
- Input: A
- Function: Last (to get the most recent value)
@@ -146,7 +146,6 @@ You can use the [TestData data source](ref:testdata-data-source) to replicate th
1. Simulate a query (`$A`) that returns latencies for each service.
Select **TestData** as the data source and configure the scenario.
- Scenario: Random Walk
- Alias: latency
- Labels: service=api-$seriesIndex
@@ -179,7 +178,6 @@ You can use the [TestData data source](ref:testdata-data-source) to replicate th
For details on CSV format requirements, see [table data examples](ref:table-data-example).
1. Add a new **Reduce** expression (`$C`).
- Type: Reduce
- Input: A
- Function: Mean
@@ -188,7 +186,6 @@ You can use the [TestData data source](ref:testdata-data-source) to replicate th
This calculates the average latency for each service: `api-0`, `api-1`, etc.
1. Add a new **Math** expression.
- Type: Math
- Expression: `$C > $B`
- Set this expression as the **alert condition**.
@@ -116,7 +116,6 @@ You can quickly experiment with multi-dimensional alerts using the [**TestData**
1. Go to **Alerting** and create an alert rule
1. Select **TestData** as the data source.
1. Configure the TestData scenario
- Scenario: **Random Walk**
- Labels: `cpu=cpu-$seriesIndex`
- Series count: 3