Documentation Plugins Cloudflare Configure

Configure the Cloudflare data source

This document explains how to configure the Cloudflare data source in Grafana.

Before you begin

Before you configure the data source, ensure you have:

• Cloudflare data source plugin installed: For installation instructions, refer to Install Grafana Enterprise plugins
• Grafana permissions: Organization administrator role
• Cloudflare API token: A user token or an account-owned token with the required permissions (see Required permissions)

Required permissions

When creating your Cloudflare API token, add the following permissions based on the features you want to use. In the Cloudflare dashboard, permissions follow the format Category > Resource > Access Level.

For security best practices:

• Only grant permissions for the features you need
• Limit scope to specific accounts or zones when possible
• Use the principle of least privilege

For more information about Cloudflare API token permissions, refer to the Cloudflare permissions documentation.

Create an API token

To create an API token in Cloudflare:

1. Go to the Cloudflare API Tokens page.
2. Click Create Token.
3. Select Create Custom Token.
4. Add the required permissions (see Required permissions).
5. Click Continue to summary, then Create Token.
6. Copy the token and paste it into the Token field in Grafana.

For detailed instructions, refer to the Cloudflare documentation.

The Cloudflare data source supports both token types:

• User tokens are verified against your Cloudflare user profile. No additional configuration is needed.
• Account-owned tokens (cfat_ prefix) are scoped to a Cloudflare account rather than a user, and are verified against that account. If you use an account-owned token, set Token type to Account-owned token in the data source configuration and enter the matching Account ID (see Configure settings).

Add the data source

To add the Cloudflare data source:

1. Click Connections in the left-side menu.
2. Click Add new connection.
3. Type Cloudflare in the search bar.
4. Select Cloudflare.
5. Click Add new data source.

Configure settings

Configure the following settings for the Cloudflare data source:

Authentication

Verify the connection

Click Save & test to verify the connection. Grafana verifies a user token against your Cloudflare user profile, and an account-owned token against the account matching the Account ID you provided under Token type: Account-owned token. A success message confirms that Grafana can connect to Cloudflare.

Provision the data source

You can define the data source in YAML files as part of the Grafana provisioning system. For more information, refer to Provision Grafana.

YAML Copy

apiVersion: 1
datasources:
  - name: Cloudflare
    type: grafana-cloudflare-datasource
    jsonData:
      variables:
        token_type: account
        account_id: <YOUR_CLOUDFLARE_ACCOUNT_ID>
    secureJsonData:
      cloudflare.token: <YOUR_CLOUDFLARE_API_TOKEN>

Replace <YOUR_CLOUDFLARE_API_TOKEN> with your Cloudflare API token. Provisioning bypasses the config editor UI, so variables.token_type and variables.account_id only matter as backend values here — omit both, or set token_type to user, when using a user token; set token_type to account and account_id to your Cloudflare account ID when using an account-owned token.

Provision with Terraform

You can provision the data source using the Grafana Terraform provider.

hcl Copy

resource "grafana_data_source" "cloudflare" {
  type = "grafana-cloudflare-datasource"
  name = "Cloudflare"

  json_data_encoded = jsonencode({
    variables = {
      token_type = "account"
      account_id = var.cloudflare_account_id
    }
  })

  secure_json_data_encoded = jsonencode({
    "cloudflare.token" = var.cloudflare_api_token
  })
}

Omit variables.token_type and variables.account_id (or set token_type to "user") when using a user token; set token_type to "account" and account_id to your Cloudflare account ID when using an account-owned token.

For more information, refer to the Grafana Terraform provider documentation.