From 9c7828e3203778325d0bc3c8c977c3c41df0de59 Mon Sep 17 00:00:00 2001 From: Larissa Wandzura Date: Wed, 27 Aug 2025 15:28:27 -0500 Subject: [PATCH] ran prettier --- .../query-transform-data/sql-expressions/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/panels-visualizations/query-transform-data/sql-expressions/index.md b/docs/sources/panels-visualizations/query-transform-data/sql-expressions/index.md index 27e98a46529..4329d85133a 100644 --- a/docs/sources/panels-visualizations/query-transform-data/sql-expressions/index.md +++ b/docs/sources/panels-visualizations/query-transform-data/sql-expressions/index.md @@ -161,7 +161,7 @@ SQL expressions integrates alerting and recording rules, allowing you to define For SQL Expressions to work properly with alerting and recording rules, your query must return: -- One numeric column - **_required_**. This contains the value that triggers alerts or gets recorded. +- One numeric column - **_required_**. This contains the value that triggers alerts or gets recorded. - One or more string columns - _optional_. These become **labels** for the alert instances or metrics. Column names and their row values become labels. Consider the following query results: