diff --git a/docs/sources/datasources/aws-cloudwatch/_index.md b/docs/sources/datasources/aws-cloudwatch/_index.md index 9cd5ed87a09..0a80cc631f7 100644 --- a/docs/sources/datasources/aws-cloudwatch/_index.md +++ b/docs/sources/datasources/aws-cloudwatch/_index.md @@ -19,97 +19,6 @@ labels: menuTitle: Amazon CloudWatch title: Amazon CloudWatch data source weight: 200 -refs: - logs: - - pattern: /docs/grafana/ - destination: /docs/grafana//panels-visualizations/visualizations/logs/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//panels-visualizations/visualizations/logs/ - explore: - - pattern: /docs/grafana/ - destination: /docs/grafana//explore/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//explore/ - provisioning-data-sources: - - pattern: /docs/grafana/ - destination: /docs/grafana//administration/provisioning/#data-sources - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//administration/provisioning/#data-sources - configure-grafana-aws: - - pattern: /docs/grafana/ - destination: /docs/grafana//setup-grafana/configure-grafana/#aws - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//setup-grafana/configure-grafana/#aws - alerting: - - pattern: /docs/grafana/ - destination: /docs/grafana//alerting/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana-cloud/alerting-and-irm/alerting/ - build-dashboards: - - pattern: /docs/grafana/ - destination: /docs/grafana//dashboards/build-dashboards/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//dashboards/build-dashboards/ - data-source-management: - - pattern: /docs/grafana/ - destination: /docs/grafana//administration/data-source-management/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//administration/data-source-management/ - configure-cloudwatch: - - pattern: /docs/grafana/ - destination: /docs/grafana//datasources/aws-cloudwatch/configure/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//datasources/aws-cloudwatch/configure/ - cloudwatch-query-editor: - - pattern: /docs/grafana/ - destination: /docs/grafana//datasources/aws-cloudwatch/query-editor/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//datasources/aws-cloudwatch/query-editor/ - cloudwatch-template-variables: - - pattern: /docs/grafana/ - destination: /docs/grafana//datasources/aws-cloudwatch/template-variables/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//datasources/aws-cloudwatch/template-variables/ - cloudwatch-aws-authentication: - - pattern: /docs/grafana/ - destination: /docs/grafana//datasources/aws-cloudwatch/aws-authentication/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//datasources/aws-cloudwatch/aws-authentication/ - query-caching: - - pattern: /docs/grafana/ - destination: /docs/grafana//administration/data-source-management/#query-and-resource-caching - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//administration/data-source-management/#query-and-resource-caching - variables: - - pattern: /docs/grafana/ - destination: /docs/grafana//dashboards/variables/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana-cloud/visualizations/dashboards/variables/ - annotate-visualizations: - - pattern: /docs/grafana/ - destination: /docs/grafana//dashboards/build-dashboards/annotate-visualizations/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana-cloud/visualizations/dashboards/build-dashboards/annotate-visualizations/ - set-up-grafana-monitoring: - - pattern: /docs/grafana/ - destination: /docs/grafana//setup-grafana/set-up-grafana-monitoring/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//setup-grafana/set-up-grafana-monitoring/ - transformations: - - pattern: /docs/grafana/ - destination: /docs/grafana//panels-visualizations/query-transform-data/transform-data/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana-cloud/visualizations/panels-visualizations/query-transform-data/transform-data/ - visualizations: - - pattern: /docs/grafana/ - destination: /docs/grafana//panels-visualizations/visualizations/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana-cloud/visualizations/panels-visualizations/visualizations/ - cloudwatch-troubleshooting: - - pattern: /docs/grafana/ - destination: /docs/grafana//datasources/aws-cloudwatch/troubleshooting/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//datasources/aws-cloudwatch/troubleshooting/ --- # Amazon CloudWatch data source @@ -120,11 +29,11 @@ Grafana includes native support for the Amazon CloudWatch plugin, so there's no The following documents will help you get started working with the CloudWatch data source: -- [Configure the CloudWatch data source](ref:configure-cloudwatch) -- [CloudWatch query editor](ref:cloudwatch-query-editor) -- [Templates and variables](ref:cloudwatch-template-variables) -- [Configure AWS authentication](ref:cloudwatch-aws-authentication) -- [Troubleshoot CloudWatch issues](ref:cloudwatch-troubleshooting) +- [Configure the CloudWatch data source](https://grafana.com/docs/grafana//datasources/aws-cloudwatch/configure/) +- [CloudWatch query editor](https://grafana.com/docs/grafana//datasources/aws-cloudwatch/query-editor/) +- [Templates and variables](https://grafana.com/docs/grafana//datasources/aws-cloudwatch/template-variables/) +- [Configure AWS authentication](https://grafana.com/docs/grafana//datasources/aws-cloudwatch/aws-authentication/) +- [Troubleshoot CloudWatch issues](https://grafana.com/docs/grafana//datasources/aws-cloudwatch/troubleshooting/) ## Import pre-configured dashboards @@ -145,7 +54,7 @@ To import curated dashboards: 1. Click **Import** for each dashboard you want to import. -![CloudWatch pre-configured dashboards Grafana v12.1](/media//docs/cloudwatch/preconfigured-dashboards-cloudwatch-v12.1.png) CloudWatch pre-configured dashboards +![CloudWatch pre-configured dashboards Grafana v12.1](/media/docs/cloudwatch/preconfigured-dashboards-cloudwatch-v12.1.png) To customize one of these dashboards, Grafana recommends saving it under a different name; otherwise, Grafana upgrades will overwrite your customizations with the new version. @@ -153,12 +62,12 @@ To customize one of these dashboards, Grafana recommends saving it under a diffe After installing and configuring the Amazon CloudWatch data source, you can: -- Create a wide variety of [visualizations](ref:visualizations) -- Configure and use [templates and variables](ref:variables) -- Add [transformations](ref:transformations) -- Add [annotations](ref:annotate-visualizations) -- Set up [alerting](ref:alerting) -- Optimize performance with [query caching](ref:query-caching) +- Create a wide variety of [visualizations](https://grafana.com/docs/grafana//panels-visualizations/visualizations/) +- Configure and use [templates and variables](https://grafana.com/docs/grafana//dashboards/variables/) +- Add [transformations](https://grafana.com/docs/grafana//panels-visualizations/query-transform-data/transform-data/) +- Add [annotations](https://grafana.com/docs/grafana//dashboards/build-dashboards/annotate-visualizations/) +- Set up [alerting](https://grafana.com/docs/grafana//alerting/) +- Optimize performance with [query caching](https://grafana.com/docs/grafana//administration/data-source-management/#query-and-resource-caching) ## Control pricing diff --git a/docs/sources/datasources/aws-cloudwatch/aws-authentication/index.md b/docs/sources/datasources/aws-cloudwatch/aws-authentication/index.md index 9259cd86e4e..2d02dc00592 100644 --- a/docs/sources/datasources/aws-cloudwatch/aws-authentication/index.md +++ b/docs/sources/datasources/aws-cloudwatch/aws-authentication/index.md @@ -16,17 +16,6 @@ labels: menuTitle: AWS authentication title: Configure AWS authentication weight: 400 -refs: - configure-grafana-assume-role-enabled: - - pattern: /docs/grafana/ - destination: /docs/grafana//setup-grafana/configure-grafana/#assume_role_enabled - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//setup-grafana/configure-grafana/#assume_role_enabled - configure-grafana-allowed-auth-providers: - - pattern: /docs/grafana/ - destination: /docs/grafana//setup-grafana/configure-grafana/#allowed_auth_providers - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//setup-grafana/configure-grafana/#allowed_auth_providers --- # Configure AWS authentication @@ -49,7 +38,7 @@ This document explores the following topics: Available authentication methods depend on your configuration and the environment where Grafana runs. -Open source Grafana enables the `AWS SDK Default`, `Credentials file`, and `Access and secret key` methods by default. Cloud Grafana enables only `Access and secret key` by default. Users with server configuration access can enable or disable specific auth providers as needed. For more information, refer to the [`allowed_auth_providers` documentation](ref:configure-grafana-allowed-auth-providers). +Open source Grafana enables the `AWS SDK Default`, `Credentials file`, and `Access and secret key` methods by default. Cloud Grafana enables only `Access and secret key` by default. Users with server configuration access can enable or disable specific auth providers as needed. For more information, refer to the [`allowed_auth_providers` documentation](https://grafana.com/docs/grafana//setup-grafana/configure-grafana/#allowed_auth_providers). - `AWS SDK Default` uses the [default provider](https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html) from the [AWS SDK for Go](https://github.com/aws/aws-sdk-go) without custom configuration. This method requires configuring AWS credentials outside Grafana through [the CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html), or by [attaching credentials directly to an EC2 instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html), [in an ECS task](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html), or for a [Service Account in a Kubernetes cluster](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html). You can attach permissions directly to the data source with AWS SDK Default or combine it with the optional [`Assume Role ARN`](#assume-a-role) field. @@ -76,7 +65,7 @@ Instead, assume role functionality lets you use one set of AWS credentials acros If the **Assume Role ARN** field is left empty, Grafana uses the provided credentials from the selected authentication method directly, and permissions to AWS data must be attached directly to those credentials. The **Assume Role ARN** field is optional for all authentication methods except for Grafana Assume Role. -To disable this feature in open source Grafana or Grafana Enterprise, refer to [`assume_role_enabled`](ref:configure-grafana-assume-role-enabled). +To disable this feature in open source Grafana or Grafana Enterprise, refer to [`assume_role_enabled`](https://grafana.com/docs/grafana//setup-grafana/configure-grafana/#assume_role_enabled). ### Use an external ID diff --git a/docs/sources/datasources/aws-cloudwatch/configure/index.md b/docs/sources/datasources/aws-cloudwatch/configure/index.md index 242b3513d47..ee9f41b6a3e 100644 --- a/docs/sources/datasources/aws-cloudwatch/configure/index.md +++ b/docs/sources/datasources/aws-cloudwatch/configure/index.md @@ -20,47 +20,11 @@ labels: menuTitle: Configure title: Configure CloudWatch weight: 100 -refs: - logs: - - pattern: /docs/grafana/ - destination: /docs/grafana//panels-visualizations/visualizations/logs/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//panels-visualizations/visualizations/logs/ - provisioning-data-sources: - - pattern: /docs/grafana/ - destination: /docs/grafana//administration/provisioning/#data-sources - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//administration/provisioning/#data-sources - configure-grafana-aws: - - pattern: /docs/grafana/ - destination: /docs/grafana//setup-grafana/configure-grafana/#aws - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//setup-grafana/configure-grafana/#aws - data-source-management: - - pattern: /docs/grafana/ - destination: /docs/grafana//administration/data-source-management/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//administration/data-source-management/ - cloudwatch-aws-authentication: - - pattern: /docs/grafana/ - destination: /docs/grafana//datasources/aws-cloudwatch/aws-authentication/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//datasources/aws-cloudwatch/aws-authentication/ - private-data-source-connect: - - pattern: /docs/grafana/ - destination: /docs/grafana-cloud/connect-externally-hosted/private-data-source-connect/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana-cloud/connect-externally-hosted/private-data-source-connect/ - configure-pdc: - - pattern: /docs/grafana/ - destination: /docs/grafana-cloud/connect-externally-hosted/private-data-source-connect/configure-pdc/#configure-grafana-private-data-source-connect-pdc - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana-cloud/connect-externally-hosted/private-data-source-connect/configure-pdc/#configure-grafana-private-data-source-connect-pdc --- # Configure the Amazon CloudWatch data source -This document provides instructions for configuring the Amazon CloudWatch data source and explains available configuration options. For general information on adding and managing data sources, refer to [Data source management](ref:data-source-management). +This document provides instructions for configuring the Amazon CloudWatch data source and explains available configuration options. For general information on adding and managing data sources, refer to [Data source management](https://grafana.com/docs/grafana//administration/data-source-management/). ## Before you begin @@ -94,7 +58,7 @@ The following are configuration options for the CloudWatch data source. Grafana plugin requests to AWS are made on behalf of an AWS Identity and Access Management (IAM) role or IAM user. The IAM user or IAM role must have the associated policies to perform certain API actions. -For authentication options and configuration details, refer to [AWS authentication](ref:cloudwatch-aws-authentication). +For authentication options and configuration details, refer to [AWS authentication](https://grafana.com/docs/grafana//datasources/aws-cloudwatch/aws-authentication/). | Setting | Description | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -137,15 +101,15 @@ You must use both an access key ID and a secret access key to authenticate. | --------------- | ----------------------------------------------------- | | **Data source** | Select the X-Ray data source from the drop-down menu. | -Grafana automatically creates a link to a trace in X-Ray data source if logs contain the `@xrayTraceId` field. To use this feature, you must already have an X-Ray data source configured. For details, see the [X-Ray data source docs](/grafana/plugins/grafana-X-Ray-datasource/). To view the X-Ray link, select the log row in either the Explore view or dashboard [Logs panel](ref:logs) to view the log details section. +Grafana automatically creates a link to a trace in X-Ray data source if logs contain the `@xrayTraceId` field. To use this feature, you must already have an X-Ray data source configured. For details, see the [X-Ray data source docs](/grafana/plugins/grafana-X-Ray-datasource/). To view the X-Ray link, select the log row in either the Explore view or dashboard [Logs panel](https://grafana.com/docs/grafana//panels-visualizations/visualizations/logs/) to view the log details section. To log the `@xrayTraceId`, refer to the [AWS X-Ray documentation](https://docs.aws.amazon.com/xray/latest/devguide/xray-services.html). To provide the field to Grafana, your log queries must also contain the `@xrayTraceId` field, for example by using the query `fields @message, @xrayTraceId`. **Private data source connect** - _Only for Grafana Cloud users._ -| Setting | Description | -| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Private data source connect** | Establishes a private, secured connection between a Grafana Cloud stack and data sources within a private network. Use the drop-down to locate the PDC URL. For setup instructions, refer to [Private data source connect (PDC)](ref:private-data-source-connect) and [Configure PDC](ref:configure-pdc). Click **Manage private data source connect** to open your PDC connection page and view your configuration details. | +| Setting | Description | +| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Private data source connect** | Establishes a private, secured connection between a Grafana Cloud stack and data sources within a private network. Use the drop-down to locate the PDC URL. For setup instructions, refer to [Private data source connect (PDC)](https://grafana.com/docs/grafana-cloud/connect-externally-hosted/private-data-source-connect/) and [Configure PDC](https://grafana.com/docs/grafana-cloud/connect-externally-hosted/private-data-source-connect/configure-pdc/#configure-grafana-private-data-source-connect-pdc). Click **Manage private data source connect** to open your PDC connection page and view your configuration details. | After configuring your Amazon CloudWatch data source options, click **Save & test** at the bottom to test the connection. You should see a confirmation dialog box that says: @@ -158,7 +122,7 @@ To troubleshoot issues while setting up the CloudWatch data source, check the `/ ### IAM policy examples To read CloudWatch metrics and EC2 tags, instances, regions, and alarms, you must grant Grafana permissions via IAM. -You can attach these permissions to the IAM role or IAM user you configured in [AWS authentication](ref:cloudwatch-aws-authentication). +You can attach these permissions to the IAM role or IAM user you configured in [AWS authentication](https://grafana.com/docs/grafana//datasources/aws-cloudwatch/aws-authentication/). **Metrics-only permissions:** @@ -309,7 +273,7 @@ You can attach these permissions to the IAM role or IAM user you configured in [ Cross-account observability lets you retrieve metrics and logs across different accounts in a single region, but you can't query EC2 Instance Attributes across accounts because those come from the EC2 API and not the CloudWatch API. {{< /admonition >}} -For more information on configuring authentication, refer to [Configure AWS authentication](ref:cloudwatch-aws-authentication). +For more information on configuring authentication, refer to [Configure AWS authentication](https://grafana.com/docs/grafana//datasources/aws-cloudwatch/aws-authentication/). ### CloudWatch Logs data protection @@ -317,7 +281,7 @@ CloudWatch Logs can protect data by applying log group data protection policies. ### Configure the data source with grafana.ini -The Grafana [configuration file](ref:configure-grafana-aws) includes an `AWS` section where you can configure data source options: +The Grafana [configuration file](https://grafana.com/docs/grafana//setup-grafana/configure-grafana/#aws) includes an `AWS` section where you can configure data source options: | Configuration option | Description | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -328,7 +292,7 @@ The Grafana [configuration file](ref:configure-grafana-aws) includes an `AWS` se ### Provision the data source You can define and configure the data source in YAML files as part of the Grafana provisioning system. -For more information about provisioning and available configuration options, refer to [Provision Grafana](ref:provisioning-data-sources). +For more information about provisioning and available configuration options, refer to [Provision Grafana](https://grafana.com/docs/grafana//administration/provisioning/#data-sources). **Using AWS SDK (default)**: diff --git a/docs/sources/datasources/aws-cloudwatch/query-editor/index.md b/docs/sources/datasources/aws-cloudwatch/query-editor/index.md index 530f177b301..e45230d21d2 100644 --- a/docs/sources/datasources/aws-cloudwatch/query-editor/index.md +++ b/docs/sources/datasources/aws-cloudwatch/query-editor/index.md @@ -18,37 +18,11 @@ labels: menuTitle: Query editor title: Amazon CloudWatch query editor weight: 200 -refs: - query-transform-data: - - pattern: /docs/grafana/ - destination: /docs/grafana//panels-visualizations/query-transform-data/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//panels-visualizations/query-transform-data/ - explore: - - pattern: /docs/grafana/ - destination: /docs/grafana//explore/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//explore/ - query-transform-data-navigate-the-query-tab: - - pattern: /docs/grafana/ - destination: /docs/grafana//panels-visualizations/query-transform-data/#navigate-the-query-tab - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//panels-visualizations/query-transform-data/#navigate-the-query-tab - alerting: - - pattern: /docs/grafana/ - destination: /docs/grafana//alerting/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana-cloud/alerting-and-irm/alerting/ - add-template-variables: - - pattern: /docs/grafana/ - destination: /docs/grafana//dashboards/variables/add-template-variables/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//dashboards/variables/add-template-variables/ --- # Amazon CloudWatch query editor -Grafana provides a query editor for the CloudWatch data source, which allows you to query, visualize, and alert on logs and metrics stored in Amazon CloudWatch. It is located on the [Explore](ref:explore) page. For general documentation on querying data sources in Grafana, refer to [Query and transform data](ref:query-transform-data). +Grafana provides a query editor for the CloudWatch data source, which allows you to query, visualize, and alert on logs and metrics stored in Amazon CloudWatch. It is located on the [Explore](https://grafana.com/docs/grafana//explore/) page. For general documentation on querying data sources in Grafana, refer to [Query and transform data](https://grafana.com/docs/grafana//panels-visualizations/query-transform-data/). ## Choose a query editing mode @@ -142,7 +116,7 @@ The query returns the average CPU utilization for all EC2 instances in the defau Auto-scaling events add new instances to the graph without manual instance ID tracking. This feature supports up to 100 metrics. -Click the [**Query inspector**](ref:query-transform-data-navigate-the-query-tab) button and select **Meta Data** to see the search expression that's automatically built to support wildcards. +Click the [**Query inspector**](https://grafana.com/docs/grafana//panels-visualizations/query-transform-data/#navigate-the-query-tab) button and select **Meta Data** to see the search expression that's automatically built to support wildcards. To learn more about search expressions, refer to the [CloudWatch documentation](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/search-expression-syntax.html). The search expression is defined by default in such a way that the queried metrics must match the defined dimension names exactly. @@ -212,7 +186,7 @@ For details about the Metrics Insights syntax, refer to the [AWS reference docum For information about Metrics Insights limits, refer to the [AWS feature documentation](https://docs.aws.amazon.com/console/cloudwatch/metricsinsights). -You can also augment queries by using [template variables](ref:add-template-variables). +You can also augment queries by using [template variables](https://grafana.com/docs/grafana//dashboards/variables/add-template-variables/). ### Use Metrics Insights keywords @@ -299,7 +273,7 @@ WHERE `@message` LIKE '%Exception%' To reference log groups in a monitoring account, use ARNs instead of LogGroup names. You can also write queries returning time series data by using the [`stats` command](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CWL_Insights-Visualizing-Log-Data.html). -When making `stats` queries in [Explore](ref:explore), ensure you are in Metrics Explore mode. +When making `stats` queries in [Explore](https://grafana.com/docs/grafana//explore/), ensure you are in Metrics Explore mode. ### Create queries for alerting @@ -318,7 +292,7 @@ filter @message like /Exception/ If you receive an error like `input data must be a wide series but got ...` when trying to alert on a query, make sure that your query returns valid numeric data that can be output to a Time series panel. {{< /admonition >}} -For more information on Grafana alerts, refer to [Alerting](ref:alerting). +For more information on Grafana alerts, refer to [Alerting](https://grafana.com/docs/grafana//alerting/). ## Cross-account observability diff --git a/docs/sources/datasources/aws-cloudwatch/template-variables/index.md b/docs/sources/datasources/aws-cloudwatch/template-variables/index.md index ee18c78593d..0efbef7ded9 100644 --- a/docs/sources/datasources/aws-cloudwatch/template-variables/index.md +++ b/docs/sources/datasources/aws-cloudwatch/template-variables/index.md @@ -17,22 +17,6 @@ labels: menuTitle: Template variables title: CloudWatch template variables weight: 300 -refs: - variable-syntax: - - pattern: /docs/grafana/ - destination: /docs/grafana//dashboards/variables/variable-syntax/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//dashboards/variables/variable-syntax/ - add-template-variables: - - pattern: /docs/grafana/ - destination: /docs/grafana//dashboards/variables/add-template-variables/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//dashboards/variables/add-template-variables/ - variables: - - pattern: /docs/grafana/ - destination: /docs/grafana//dashboards/variables/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//dashboards/variables/ --- # CloudWatch template variables @@ -42,7 +26,7 @@ Grafana lists these variables in drop-down select boxes at the top of the dashbo -For an introduction to templating and template variables, refer to [Templating](ref:variables) and [Add and manage variables](ref:add-template-variables). +For an introduction to templating and template variables, refer to [Templating](https://grafana.com/docs/grafana//dashboards/variables/) and [Add and manage variables](https://grafana.com/docs/grafana//dashboards/variables/add-template-variables/). ## Use query variables @@ -69,7 +53,7 @@ For details about the metrics CloudWatch provides, refer to the [CloudWatch docu ### Use variables in queries Use the Grafana variable syntax to include variables in queries. A query variable in dynamically retrieves values from your data source using a query. -For details, refer to the [variable syntax documentation](ref:variable-syntax). +For details, refer to the [variable syntax documentation](https://grafana.com/docs/grafana//dashboards/variables/variable-syntax/). ## Use ec2_instance_attribute diff --git a/docs/sources/datasources/aws-cloudwatch/troubleshooting/index.md b/docs/sources/datasources/aws-cloudwatch/troubleshooting/index.md index 77ce4106bf8..91458d9091c 100644 --- a/docs/sources/datasources/aws-cloudwatch/troubleshooting/index.md +++ b/docs/sources/datasources/aws-cloudwatch/troubleshooting/index.md @@ -18,37 +18,11 @@ labels: menuTitle: Troubleshooting title: Troubleshoot Amazon CloudWatch data source issues weight: 500 -refs: - configure-cloudwatch: - - pattern: /docs/grafana/ - destination: /docs/grafana//datasources/aws-cloudwatch/configure/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//datasources/aws-cloudwatch/configure/ - cloudwatch-aws-authentication: - - pattern: /docs/grafana/ - destination: /docs/grafana//datasources/aws-cloudwatch/aws-authentication/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//datasources/aws-cloudwatch/aws-authentication/ - cloudwatch-template-variables: - - pattern: /docs/grafana/ - destination: /docs/grafana//datasources/aws-cloudwatch/template-variables/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//datasources/aws-cloudwatch/template-variables/ - cloudwatch-query-editor: - - pattern: /docs/grafana/ - destination: /docs/grafana//datasources/aws-cloudwatch/query-editor/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana//datasources/aws-cloudwatch/query-editor/ - private-data-source-connect: - - pattern: /docs/grafana/ - destination: /docs/grafana-cloud/connect-externally-hosted/private-data-source-connect/ - - pattern: /docs/grafana-cloud/ - destination: /docs/grafana-cloud/connect-externally-hosted/private-data-source-connect/ --- # Troubleshoot Amazon CloudWatch data source issues -This document provides solutions to common issues you may encounter when configuring or using the Amazon CloudWatch data source. For configuration instructions, refer to [Configure CloudWatch](ref:configure-cloudwatch). +This document provides solutions to common issues you may encounter when configuring or using the Amazon CloudWatch data source. For configuration instructions, refer to [Configure CloudWatch](https://grafana.com/docs/grafana//datasources/aws-cloudwatch/configure/). {{< admonition type="note" >}} The data source health check validates both metrics and logs permissions. If your IAM policy only grants access to one of these (for example, metrics-only or logs-only), the health check displays a red status. However, the service you have permissions for is still usable—you can query metrics or logs based on whichever permissions are configured. @@ -68,13 +42,13 @@ These errors occur when AWS credentials are invalid, missing, or don't have the **Possible causes and solutions:** -| Cause | Solution | -| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| IAM policy missing required permissions | Attach the appropriate IAM policy to your user or role. For metrics, you need `cloudwatch:ListMetrics`, `cloudwatch:GetMetricData`, and related permissions. For logs, you need `logs:DescribeLogGroups`, `logs:StartQuery`, `logs:GetQueryResults`, and related permissions. Refer to [Configure CloudWatch](ref:configure-cloudwatch) for complete policy examples. | -| Incorrect access key or secret key | Verify the credentials in the AWS Console under **IAM** > **Users** > your user > **Security credentials**. Generate new credentials if necessary. | -| Credentials have expired | For temporary credentials, generate new ones. For access keys, verify they haven't been deactivated or deleted. | -| Wrong AWS region | Verify the default region in the data source configuration matches where your resources are located. | -| Assume Role ARN is incorrect | Verify the role ARN format: `arn:aws:iam:::role/`. Check that the role exists in the AWS Console. | +| Cause | Solution | +| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| IAM policy missing required permissions | Attach the appropriate IAM policy to your user or role. For metrics, you need `cloudwatch:ListMetrics`, `cloudwatch:GetMetricData`, and related permissions. For logs, you need `logs:DescribeLogGroups`, `logs:StartQuery`, `logs:GetQueryResults`, and related permissions. Refer to [Configure CloudWatch](https://grafana.com/docs/grafana//datasources/aws-cloudwatch/configure/) for complete policy examples. | +| Incorrect access key or secret key | Verify the credentials in the AWS Console under **IAM** > **Users** > your user > **Security credentials**. Generate new credentials if necessary. | +| Credentials have expired | For temporary credentials, generate new ones. For access keys, verify they haven't been deactivated or deleted. | +| Wrong AWS region | Verify the default region in the data source configuration matches where your resources are located. | +| Assume Role ARN is incorrect | Verify the role ARN format: `arn:aws:iam:::role/`. Check that the role exists in the AWS Console. | ### "Unable to assume role" @@ -130,7 +104,7 @@ These errors occur when AWS credentials are invalid, missing, or don't have the - ECS task role (if running in ECS) - EKS service account (if running in EKS) 1. Ensure the Grafana process has permission to read the credentials file. -1. For EKS with IRSA, set the pod's security context to allow user 472 (grafana) to access the projected token. Refer to [AWS authentication](ref:cloudwatch-aws-authentication) for details. +1. For EKS with IRSA, set the pod's security context to allow user 472 (grafana) to access the projected token. Refer to [AWS authentication](https://grafana.com/docs/grafana//datasources/aws-cloudwatch/aws-authentication/) for details. ### Credentials file not found @@ -163,7 +137,7 @@ These errors occur when Grafana cannot reach AWS CloudWatch endpoints. 1. Verify network connectivity from the Grafana server to AWS endpoints. 1. Check firewall rules allow outbound HTTPS (port 443) to AWS services. 1. If using a VPC, ensure proper NAT gateway or VPC endpoint configuration. -1. For Grafana Cloud connecting to private resources, configure [Private data source connect](ref:private-data-source-connect). +1. For Grafana Cloud connecting to private resources, configure [Private data source connect](https://grafana.com/docs/grafana-cloud/connect-externally-hosted/private-data-source-connect/). 1. Check if the default region is correct—incorrect regions may cause longer timeouts. 1. Increase the timeout settings if queries involve large data volumes. @@ -360,7 +334,7 @@ These errors occur when using template variables with the CloudWatch data source 1. For dependent variables, ensure parent variables have valid selections. 1. Verify the region is set correctly (use "default" for the data source's default region). -For more information on template variables, refer to [CloudWatch template variables](ref:cloudwatch-template-variables). +For more information on template variables, refer to [CloudWatch template variables](https://grafana.com/docs/grafana//datasources/aws-cloudwatch/template-variables/). ### Multi-value template variables cause query failures