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]
co-authored by
Ashley Harrison
Ashley Harrison
parent
20cea80795
commit
c94f930950
@@ -130,7 +130,6 @@ The following settings are specific to the Elasticsearch data source.
|
||||
- **Index name** - Use the index settings to specify a default for the `time field` and your Elasticsearch index's name. You can use a time pattern, for example `[logstash-]YYYY.MM.DD`, or a wildcard for the index name. When specifying a time pattern, the fixed part(s) of the pattern should be wrapped in square brackets.
|
||||
|
||||
- **Pattern** - Select the matching pattern if using one in your index name. Options include:
|
||||
|
||||
- no pattern
|
||||
- hourly
|
||||
- daily
|
||||
|
||||
@@ -61,7 +61,6 @@ Metrics queries aggregate data and produce a variety of calculations such as cou
|
||||
- **Alias** - Aliasing only applies to **time series queries**, where the last group is `date histogram`. This is ignored for any other type of query.
|
||||
|
||||
- **Metric** - Metrics aggregations include:
|
||||
|
||||
- count - see [Value count aggregation](https://www.elastic.co/guide/en/elasticsearch/reference/8.9/search-aggregations-metrics-valuecount-aggregation.html)
|
||||
- average - see [Avg aggregation](https://www.elastic.co/guide/en/elasticsearch/reference/8.9/search-aggregations-metrics-rate-aggregation.html)
|
||||
- sum - see [Sum aggregation](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-metrics-sum-aggregation.html)
|
||||
@@ -78,7 +77,6 @@ You can select multiple metrics and group by multiple terms or filters when usin
|
||||
Use the **+ sign** to the right to add multiple metrics to your query. Click on the **eye icon** next to **Metric** to hide metrics, and the **garbage can icon** to remove metrics.
|
||||
|
||||
- **Group by options** - Create multiple group by options when constructing your Elasticsearch query. Date histogram is the default option. Below is a list of options in the dropdown menu.
|
||||
|
||||
- terms - see [Terms aggregation](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-terms-aggregation.html).
|
||||
- filter - see [Filter aggregation](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-filter-aggregation.html).
|
||||
- geo hash grid - see [Geohash grid aggregation](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-geohashgrid-aggregation.html).
|
||||
|
||||
@@ -83,7 +83,6 @@ If Grafana is running on a Google Compute Engine (GCE) virtual machine, when you
|
||||
Before you can request data from Google Cloud Monitoring, you must first enable necessary APIs on the Google end.
|
||||
|
||||
1. Open the Monitoring and Cloud Resource Manager API pages:
|
||||
|
||||
- [Monitoring API](https://console.cloud.google.com/apis/library/monitoring.googleapis.com)
|
||||
- [Cloud Resource Manager API](https://console.cloud.google.com/apis/library/cloudresourcemanager.googleapis.com)
|
||||
|
||||
|
||||
@@ -89,7 +89,6 @@ The following components will help you build a MySQL query:
|
||||
- **Format** - Select a format response from the drop-down for the MySQL query. The default is **Table**. If you use the **Time series** format option, one of the columns must be `time`.
|
||||
|
||||
- **Dataset** - Select a database to query from the drop-down.
|
||||
|
||||
- **Table** - Select a table from the drop-down. Tables correspond to the chosen database.
|
||||
|
||||
- **Data operations** - _Optional_ Select an aggregation from the drop-down. You can add multiple data operations by clicking the **+ sign**. Click the **X** to remove a data operation. Click the **garbage can icon** to remove the entire column.
|
||||
@@ -99,15 +98,12 @@ The following components will help you build a MySQL query:
|
||||
- **Alias** - _Optional_ Add an alias from the drop-down. You can also add your own alias by typing it in the box and clicking **Enter**. Remove an alias by clicking the **X**.
|
||||
|
||||
- **Filter** - Toggle to add filters.
|
||||
|
||||
- **Filter by column value** - _Optional_ If you toggle **Filter** you can add a column to filter by from the drop-down. To filter on more columns, click the **+ sign** to the right of the condition drop-down. You can choose a variety of operators from the drop-down next to the condition. When multiple filters are added you can add an `AND` operator to display all true conditions or an `OR` operator to display any true conditions. Use the second drop-down to choose a filter. To remove a filter, click the `X` button next to that filter's drop-down. After selecting a date type column, you can choose **Macros** from the operators list and select `timeFilter` which will add the `$\_\_timeFilter` macro to the query with the selected date column.
|
||||
|
||||
- **Group** - Toggle to add **Group by column**.
|
||||
|
||||
- **Group by column** - Select a column to filter by from the drop-down. Click the **+ sign** to filter by multiple columns. Click the **X** to remove a filter.
|
||||
|
||||
- **Order** - Toggle to add an ORDER BY statement.
|
||||
|
||||
- **Order by** - Select a column to order by from the drop-down. Select ascending (`ASC`) or descending (`DESC`) order.
|
||||
- **Limit** - You can add an optional limit on the number of retrieved results. Default is 50.
|
||||
|
||||
|
||||
@@ -148,7 +148,6 @@ Use the IP address of the Prometheus container, or the hostname if you are using
|
||||
There are three authentication options for the Prometheus data source.
|
||||
|
||||
- **Basic authentication** - The most common authentication method.
|
||||
|
||||
- **User** - The username you use to connect to the data source.
|
||||
- **Password** - The password you use to connect to the data source.
|
||||
|
||||
|
||||
@@ -78,7 +78,6 @@ The following video demonstrates how to use the visual Prometheus query builder:
|
||||
Builder mode contains the following components:
|
||||
|
||||
- **Kick start your query** - Click to view a list of predefined operation patterns that help you quickly build queries with multiple operations. These include:
|
||||
|
||||
- Rate query starters
|
||||
- Histogram query starters
|
||||
- Binary query starters
|
||||
@@ -104,7 +103,6 @@ Click **+ Operations** to select from a list of operations including Aggregation
|
||||
**Options:**
|
||||
|
||||
- **Legend**- Lets you customize the name for the time series. You can use a predefined or custom format.
|
||||
|
||||
- **Auto** - Displays unique labels. Also displays all overlapping labels if a series has multiple labels.
|
||||
- **Verbose** - Displays all label names.
|
||||
- **Custom** - Lets you customize the legend using label templates. For example, `{{hostname}}` is replaced with the value of the `hostname` label. To switch to a different legend mode, clear the input and click outside the field.
|
||||
@@ -112,7 +110,6 @@ Click **+ Operations** to select from a list of operations including Aggregation
|
||||
- **Min step** - Sets the minimum interval between data points returned by the query. For example, setting this to `1h` suggests that data is collected or displayed at hourly intervals. This setting supports the `$__interval` and `$__rate_interval` macros. Note that the time range of the query is aligned to this step size, which may adjust the actual start and end times of the returned data.
|
||||
|
||||
- **Format** - Determines how the data from your Prometheus query is interpreted and visualized in a panel. Choose from the following format options:
|
||||
|
||||
- **Time series** - The default format. Refer to [Time series kind formats](https://grafana.com/developers/dataplane/timeseries/) for information on time series data frames and how time and value fields are structured.
|
||||
- **Table** - Displays data in table format. This format works only in a [Table panel](ref:table).
|
||||
- **Heatmap** - Displays Histogram-type metrics in a [Heatmap panel](ref:heatmap) by converting cumulative histograms to regular ones and sorting the series by the bucket bound. Converts cumulative histogram data into regular histogram format and sorts the series by bucket boundaries for proper display.
|
||||
|
||||
@@ -235,7 +235,6 @@ To use custom queries with the configuration, follow these steps:
|
||||
1. Specify a custom query to be used to query metrics data.
|
||||
|
||||
Each linked query consists of:
|
||||
|
||||
- **Link Label:** _(Optional)_ Descriptive label for the linked query.
|
||||
- **Query:** The query ran when navigating from a trace to the metrics data source.
|
||||
Interpolate tags using the `$__tags` keyword.
|
||||
|
||||
@@ -45,7 +45,6 @@ To use trace correlations, you need:
|
||||
1. On step 1, provide a **label** for the correlation, and an optional **description**.
|
||||
|
||||
1. On step 2, configure the correlation **target**.
|
||||
|
||||
- Select the **Type** drop-down list and choose **Query** to link to another data source or choose **External** for a custom URL.
|
||||
|
||||
- For a query **Target**, select the target drop-down list and select the data source that should be queried when the link is clicked. Define the target query.
|
||||
@@ -68,7 +67,6 @@ To use trace correlations, you need:
|
||||
{{< figure src="/media/docs/tempo/screenshot-grafana-trace-correlations-loki-step-2.png" max-width="900px" class="docs-image--no-shadow" alt="Setting up a correlation for a Loki target using trace variables" >}}
|
||||
|
||||
1. On step 3, configure the correlation data source:
|
||||
|
||||
- Select your Tempo data source in the **Source** drop-down list.
|
||||
|
||||
- Enter the trace data variable you use for the correlation in the **Results field**.
|
||||
@@ -104,7 +102,6 @@ In this example, you configure trace to logs by service name and a trace identif
|
||||
{{< figure src="/media/docs/tempo/screenshot-grafana-trace-view-correlations-example-1-step-1.png" max-width="900px" class="docs-image--no-shadow" alt="Using correlations for a trace" >}}
|
||||
|
||||
1. On step 2, configure the correlation target:
|
||||
|
||||
- Select the target type **Query** and select your Loki data source as **Target**.
|
||||
|
||||
- Define the Loki query, using `serviceName` and `traceID` as variables derived from the span data:
|
||||
@@ -116,7 +113,6 @@ In this example, you configure trace to logs by service name and a trace identif
|
||||
{{< figure src="/media/docs/tempo/screenshot-grafana-trace-view-correlations-example-1-step-2.png" max-width="900px" class="docs-image--no-shadow" alt="Using correlations for a trace" >}}
|
||||
|
||||
1. On step 3, configure the correlation source:
|
||||
|
||||
- Select your Tempo data source as **Source**.
|
||||
|
||||
- Use `traceID` as **Results field**.
|
||||
@@ -138,7 +134,6 @@ In this example, you configure trace corrections with a custom URL.
|
||||
1. On step 1, add a new correlation with the label **Open custom URL** and an optional description.
|
||||
|
||||
1. On step 2, configure the correlation target:
|
||||
|
||||
- Select the target type **External**.
|
||||
|
||||
- Define your target URL, using variables derived from the span data. In this example, we are using `serviceName` and `traceID`.
|
||||
@@ -148,7 +143,6 @@ In this example, you configure trace corrections with a custom URL.
|
||||
```
|
||||
|
||||
1. On step 3, configure the correlation source:
|
||||
|
||||
- Select your Tempo data source as **Source**.
|
||||
|
||||
- Use `traceID` as **Results field**.
|
||||
|
||||
Reference in New Issue
Block a user