remove unnecessary version notices (#94839)
This commit is contained in:
Robby Milo
@@ -121,10 +121,6 @@ For details on AWS SigV4, refer to the [AWS documentation](https://docs.aws.amaz
|
||||
|
||||
### AWS Signature Version 4 authentication
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana v7.3 and higher.
|
||||
{{% /admonition %}}
|
||||
|
||||
To sign requests to your Amazon Elasticsearch Service domain, you can enable SigV4 in Grafana's [configuration](ref:configuration).
|
||||
|
||||
Once AWS SigV4 is enabled, you can configure it on the Elasticsearch data source configuration page.
|
||||
|
||||
@@ -198,10 +198,6 @@ An expected result would look like: `gce_instance - compute.googleapis.com/insta
|
||||
|
||||
### Deep-link from Grafana panels to the Google Cloud Console Metrics Explorer
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana v7.1 and higher.
|
||||
{{% /admonition %}}
|
||||
|
||||
{{< figure src="/static/img/docs/v71/cloudmonitoring_deep_linking.png" max-width="500px" class="docs-image--no-shadow" caption="Google Cloud Monitoring deep linking" >}}
|
||||
|
||||
You can click on a time series in the panel to access a context menu, which contains a link to **View in Metrics Explorer in Google Cloud Console**.
|
||||
@@ -222,10 +218,6 @@ If the query editor rows return different units, Grafana uses the unit from the
|
||||
|
||||
### Use the Monitoring Query Language
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana v7.4 and higher.
|
||||
{{% /admonition %}}
|
||||
|
||||
The Monitoring Query Language (MQL) query builder helps you query and display MQL results in time series format.
|
||||
To understand basic MQL concepts, refer to [Introduction to Monitoring Query Language](https://cloud.google.com/monitoring/mql).
|
||||
|
||||
@@ -245,10 +237,6 @@ However, `{{metric.service}}` is not supported, and `{{metric.type}}` and `{{met
|
||||
|
||||
## Query Service Level Objectives
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana v7.0 and higher.
|
||||
{{% /admonition %}}
|
||||
|
||||
{{< figure src="/static/img/docs/google-cloud-monitoring/slo-query-builder-8-0.png" max-width="400px" class="docs-image--no-shadow" caption="Service Level Objectives (SLO) query editor" >}}
|
||||
|
||||
The SLO query builder helps you visualize SLO data in time series format.
|
||||
|
||||
@@ -125,10 +125,6 @@ For example, `apps.$app.servers.*` uses the variable `$app` in its query definit
|
||||
|
||||
### Use `__searchFilter` to filter query variable results
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana v6.5 and higher.
|
||||
{{% /admonition %}}
|
||||
|
||||
You can use `__searchFilter` in the query field to filter the query result based on what the user types in the dropdown select box.
|
||||
The default value for `__searchFilter` is `*` if you've not entered anything, and `` when used as part of a regular expression.
|
||||
|
||||
|
||||
@@ -110,7 +110,6 @@ You can also configure settings specific to the Jaeger data source. These option
|
||||
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana v7.4 and higher.
|
||||
If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
|
||||
{{% /admonition %}}
|
||||
|
||||
|
||||
@@ -252,10 +252,6 @@ In your `server` section, add the following configuration:
|
||||
}
|
||||
```
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana v6.3 and higher.
|
||||
{{% /admonition %}}
|
||||
|
||||
## Create a metric query
|
||||
|
||||
You can use LogQL to wrap a log query with functions that create metrics from your logs.
|
||||
|
||||
@@ -393,8 +393,6 @@ ORDER BY 1
|
||||
|
||||
**Example region query using time and timeend columns with epoch values:**
|
||||
|
||||
> Only available in Grafana v6.6+.
|
||||
|
||||
```sql
|
||||
SELECT
|
||||
time_sec as time,
|
||||
|
||||
@@ -99,7 +99,7 @@ Administrators can also [configure the data source via YAML](#provision-the-data
|
||||
| **Session Timezone** | Specifies the timezone used in the database session, such as `Europe/Berlin` or `+02:00`. Required if the timezone of the database (or the host of the database) is set to something other than UTC. Set this to `+00:00` so Grafana can handle times properly. Set the value used in the session with `SET time_zone='...'`. If you leave this field empty, the timezone will not be updated. For more information, refer to [MySQL Server Time Zone Support](https://dev.mysql.com/doc/en/time-zone-support.html). |
|
||||
| **Max open** | The maximum number of open connections to the database, default `100` (Grafana v5.4+). |
|
||||
| **Max idle** | The maximum number of connections in the idle connection pool, default `100` (Grafana v5.4+). |
|
||||
| **Auto (max idle)** | Toggle to set the maximum number of idle connections to the number of maximum open connections (available in Grafana v9.5.1+). Default is `true`. |
|
||||
| **Auto (max idle)** | Toggle to set the maximum number of idle connections to the number of maximum open connections. Default is `true`. |
|
||||
| **Allow cleartext passwords** | Allows the use of the [cleartext client side plugin](https://dev.mysql.com/doc/en/cleartext-pluggable-authentication.html) as required by a specific type of account, such as one defined with the [PAM authentication plugin](https://dev.mysql.com/doc/en/pam-pluggable-authentication.html). <br />**Sending passwords in clear text may be a security problem in some configurations**. To avoid password issues, it is recommended that clients connect to a MySQL server using a method that protects the password. Possibilities include [TLS / SSL](https://github.com/go-sql-driver/mysql#tls), IPsec, or a private network. Default is `false`. |
|
||||
| **Max lifetime** | The maximum amount of time in seconds a connection may be reused. This should always be lower than configured [wait_timeout](https://dev.mysql.com/doc/en/server-system-variables.html#sysvar_wait_timeout) in MySQL (Grafana v5.4+). The default is `14400` or 4 hours. |
|
||||
|
||||
@@ -568,8 +568,6 @@ WHERE
|
||||
|
||||
**Example region query using time and timeend columns with epoch values:**
|
||||
|
||||
> Only available in Grafana v6.6+.
|
||||
|
||||
```sql
|
||||
SELECT
|
||||
epoch_time as time,
|
||||
|
||||
@@ -487,8 +487,6 @@ WHERE
|
||||
|
||||
**Example region query using time and timeend columns with epoch values:**
|
||||
|
||||
> Only available in Grafana v6.6+.
|
||||
|
||||
```sql
|
||||
SELECT
|
||||
epoch_time as time,
|
||||
|
||||
@@ -171,10 +171,6 @@ For details on AWS SigV4, refer to the [AWS documentation](https://docs.aws.amaz
|
||||
|
||||
### AWS Signature Version 4 authentication
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana v7.3.5 and higher.
|
||||
{{% /admonition %}}
|
||||
|
||||
To connect the Prometheus data source to Amazon Managed Service for Prometheus using SigV4 authentication, refer to the AWS guide to [Set up Grafana open source or Grafana Enterprise for use with AMP](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-query-standalone-grafana.html).
|
||||
|
||||
If you run Grafana in an Amazon EKS cluster, follow the AWS guide to [Query using Grafana running in an Amazon EKS cluster](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-query-grafana-7.3.html).
|
||||
|
||||
@@ -143,7 +143,7 @@ Click **Inspector** to get detailed statistics regarding your query. Inspector f
|
||||
|
||||
**Builder mode** helps you build queries using a visual interface. This option is best for users who have limited or no previous experience working with Prometheus and PromQL.
|
||||
|
||||
This video demonstrates how to use the visual Prometheus query builder available in Grafana v9.0:
|
||||
This video demonstrates how to use the visual Prometheus query builder:
|
||||
|
||||
{{< vimeo 720004179 >}}
|
||||
|
||||
|
||||
@@ -109,10 +109,6 @@ Regex:
|
||||
|
||||
## Use `$__rate_interval`
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana v7.2 and higher.
|
||||
{{% /admonition %}}
|
||||
|
||||
We recommend using `$__rate_interval` in the `rate` and `increase` functions instead of `$__interval` or a fixed interval value.
|
||||
Because `$__rate_interval` is always at least four times the value of the Scrape interval, it avoid problems specific to Prometheus.
|
||||
|
||||
|
||||
@@ -103,7 +103,6 @@ To configure basic settings for the data source, complete the following steps:
|
||||
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana v7.4 and higher.
|
||||
If you use Grafana Cloud, open a [support ticket in the Cloud Portal](/profile/org#support) to access this feature.
|
||||
{{% /admonition %}}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user