Skip to content
Visit Logs on GitHub
Set theme to dark (⇧+D)


This tutorial explains how to analyze Cloudflare Logs using the Cloudflare App for Splunk.


If you haven’t used Cloudflare Logs before, visit our Logs documentation for more details. Contact your Cloudflare Customer Account Team to enable logs for your account.

This tutorial describes how to get Cloudflare logs from Amazon S3 into Splunk using the Splunk Add-on for Amazon Web Services. To learn how to use Logpush to send logs to AWS S3, refer to the Logpush documentation. Alternatively, you can use Logpull to get logs to your Splunk HTTP Event Collector directly and skip Task 1.


Before sending your Cloudflare log data to Splunk, make sure that you:

Task 1 - Connect AWS S3 to Splunk

Before completing this task, make sure you’ve enabled Cloudflare Logpush on AWS S3.

To start receiving Cloudflare log data, you need to connect AWS S3 to Splunk as follows:

  1. Log in to your Splunk instance > Apps > Find More Apps.

  2. Search for Splunk Add-on for Amazon Web Services.

  3. Use your Splunk account login credentials to download and install the application. Splunk add-on for AWS

  4. Once installed, restart and reopen your Splunk instance.

  5. Next, click Configuration and enter your AWS account Key ID and Secret Key. We recommend creating a separate AWS user account with an AmazonS3ReadOnlyAccess policy. Splunk add-on AWS info

  6. In Configurations, click Create New Input > S3 Access Logs > Generic S3, and enter the following:

    • Name: cloudflare-logs-s3

    • AWS Account: Enter the read-only AWS account you created for the Splunk instance.

    • Assume role: Optional

    • S3 bucket: From the drop down menu, select the S3 bucket containing the Cloudflare logs.

    • S3 Key Prefix: Leave empty.

    • Source Type: Enter _cloudflare:json_or if disabled, see Step 7 below.

    • Index: Enter _cloudflare._You can use an existing index or create a new one as described in Step 8 below.

    • Advanced Settings > Polling Interval: Enter 300. Splunk add-on AWS info

  7. If the field is inactive and you can’t update the default value aws:s3:accesslogs,_as shown in the screenshot above,_update the Source Type manually by going to Settings > Data Inputs > Select AWS S3 and open your current AWS S3 connection. Splunk settings for AWS S3 ata inputs Splunk update AWS S3 source to Cloudflare Scroll down and select More Settings. Manually update field Source type to the value _cloudflare:json_and click Save. Splunk update AWS S3 source type

  8. To create a new index go to Settings > Indexes > New Index, then enter _cloudflare_as the Index Name and leave the default settings or update them according to your preferences. Then, click Save. Splunk create new index Splunk add new index name

Now, logs should be loading into Splunk. You can verify this under Splunk Add-on for AWS > Search. In the search box, type:

index=* sourcetype=cloudflare:json

Next, select the desired time interval and and click Search.

If everything is configured correctly, you should be able to see Cloudflare logs as shown in the screenshot below.

Splunk add-on search

Task 2 - Install and Configure the Cloudflare App for Splunk

To install the Cloudflare App for Splunk:

  1. Login to your Splunk instance.
  2. Under Apps > Find More Apps search for Cloudflare App for Splunk.
  3. Click Install.

Splunk find Cloudflare app

Once installed, you need to configure the application. To do this, a set up page is included with the application:

  1. Open the set up screen by clicking the Apps dropdown, then Manage Apps > Cloudflare Set Up.
  2. Enter the Index name where the Cloudflare JSON logs are stored. This value must be entered in the format index=index_name. By default the value is set to index=cloudflare.
  3. Optional: Enable Data Model Acceleration. This option is disabled by default.

Splunk configure Cloudflare app

The Cloudflare App is now installed and the dashboards should be populating with data.

Post Installation Notes

You can change the Index Name after initial configuration by accessing the app Set up page by clicking on the Apps dropdown, then Manage Apps > Cloudflare App for Splunk > Set up.

Splunk apps set up interface

Also, you can find the Index Name manually by visiting Settings > Advanced search > Search macros.

Splunk search macros

The Cloudflare App for Splunk comes with a custom Cloudflare Data Model which has an acceleration time frame of 1 day but is not accelerated by default. If you enable Data Model acceleration, we recommend that the Data Model is only accelerated for 1 or 7 days to ensure there are no adverse effects within your Splunk environment.

You can enable or disable acceleration after the initial configuration by accessing the app Set up page by clicking the Apps dropdown, then Manage Apps > Cloudflare Set Up.

Splunk search macros

You can also manually configure Data Models by going to Settings > Data models. Learn more about data model acceleration here.

Task 3 - View the Dashboards

You can analyze Cloudflare logs with the thirteen (13) dashboards listed below.

You can use filters within these dashboards to help narrow the analysis by date and time, device type, country, user agent, client IP, hostname, and more to further help with debugging and tracing.

About the Dashboards

The following dashboards outlined below are available as part of the Cloudflare App for Splunk.

Cloudflare - Snapshot

Web Traffic Overview and Web Traffic Types: Get an overview of the most important metrics from your websites and applications on the Cloudflare network. Splunk dashboard Cloudflare Snapshot

Cloudflare - Reliability

Summary and Detailed: Get insights on the availability of your websites and applications. Metrics include origin response error ratio, origin response status over time, percentage of 3xx/4xx/5xx errors over time, and more. Splunk dashboard Cloudflare Reliability Summary

Splunk dashboard Cloudflare Reliability Detailed

Cloudflare - Security

Overview: Get insights on threats to your websites and applications, including number of threats stopped, threats over time, top threat countries, and more. Splunk dashboard Cloudflare Security Overview

WAF: Get insights on threat identification and mitigation by our Web Application Firewall, including events like SQL injections, XSS, and more. Use this data to fine tune the firewall to target obvious threats and prevent false positives. Splunk dashboard Cloudflare Security WAF

Rate Limiting: Get insights on rate limiting protection against denial-of-service attacks, brute-force login attempts, and other types of abusive behavior targeted at your websites or applications. Splunk dashboard Cloudflare Security Rate Limiting

Bots Summary and Bots Detailed: Investigate bot activity on your website to prevent content scraping, checkout fraud, spam registration and other malicious activities. Splunk dashboard Cloudflare Security Bots Summary

Splunk dashboard Cloudflare Security Bots Detailed

Cloudflare - Performance

Requests and Cache and Bandwidth: Identify and address performance issues and caching misconfigurations. Metrics include total vs. cached bandwidth, saved bandwidth, total requests, cache ratio, top uncached requests, and more. Splunk dashboard Cloudflare Performance Requests and Cache

Splunk dashboard Cloudflare Performance Bandwidth

Hostname, Content Type, Request Methods, Connection Type: Get insights into your most popular hostnames, most requested content types, breakdown of request methods, and connection type.

Splunk dashboard Cloudflare Performance Hostname, Content Type, Request Methods, Connection Type

Static vs. Dynamic Content: Get insights into the performance of your static and dynamic content, including slowest URLs. Splunk dashboard Cloudflare Performance Static vs. Dynamic Content


All dashboard have a set of filters that you can apply to the entire dashboard, as shown in the following example. Filters are applied across the entire dashboard.

Splunk Cloudflare filters

You can use filters to drill down and examine the data at a granular level. Filters include client country, client device type, client IP, client request host, client request URI, client request user agent, edge response status, origin IP, and origin response status.

The default time interval is set to 24 hours. Note that for correct calculations filter will need to exclude Worker subrequests (WorkerSubrequest = false) and purge requests (ClientRequestMethod is not PURGE).

Available Filters:

  • Time Range (EdgeStartTimestamp)

  • Client Country

  • Client Device type

  • Client IP

  • Client Request Host

  • Client Request URI

  • Client Request User Agent

  • Edge response status

  • Origin IP

  • Origin Response Status

  • RayID

  • Worker Subrequest

  • Client Request Method

Debugging tips

Incomplete dashboards

The Splunk Cloudflare App relies on data from the Cloudflare Enterprise Logs fields outlined below. Depending on which fields you have enabled, certain dashboards might not populate fully.

If that is the case, verify and test the Cloudflare App filters below each dashboard (these filters are the same across all dashboards). You can delete any filters that you don’t need, even if such filters include data fields already contained in your logs.

Also, you could compare the list of fields you are getting in Cloudflare Logs with the fields listed in Splunk > Settings > Data Model > Cloudflare.

The available fields are:

  • CacheCacheStatus

  • CacheResponseBytes

  • CacheResponseStatus

  • ClientASN

  • ClientCountry

  • ClientDeviceType

  • ClientIP

  • ClientIPClass

  • ClientRequestBytes

  • ClientRequestHost

  • ClientRequestMethod

  • ClientRequestPath

  • ClientRequestProtocol

  • ClientRequestReferer

  • ClientRequestURI

  • ClientRequestUserAgent

  • ClientSSLCipher

  • ClientSSLProtocol

  • ClientSrcPort

  • EdgeColoCode

  • EdgeColoID

  • EdgeEndTimestamp

  • EdgePathingOp

  • EdgePathingSrc

  • EdgePathi

  • ngStatus

  • EdgeRateLimitAction

  • EdgeRateLimitID

  • EdgeRequestHost

  • EdgeResponseBytes

  • EdgeResponseContentType

  • EdgeResponseStatus

  • EdgeServerIP

  • EdgeStartTimestamp

  • FirewallMatchesActions

  • FirewallMatchesSources

  • FirewallMatchesRuleIDs

  • OriginIP

  • OriginResponseStatus

  • OriginResponseTime

  • OriginSSLProtocol

  • RayID

  • WAFAction

  • WAFFlags

  • WAFMatchedVar

  • WAFProfile

  • WAFRuleID

  • WAFRuleMessage

  • WorkerSubrequest

  • ZoneID