Skip to main content

Overview

The integration uses a Cloudflare Logpush job to send HTTP request logs to our Agent Analytics API. Cloudflare Logpush forwards Cloudflare logs to a non-Cloudflare destination such as Profound. It is available on all Cloudflare plans. See Cloudflare’s Logpush documentation for more information.

Prerequisites

  • A Cloudflare account
  • Access to your domain’s Cloudflare configuration
  • A Profound Log Ingestion Token for Agent Analytics
To use a Cloudflare Worker instead, see our integration guide using Cloudflare Workers.
Logpush Detected

Configuration

1

Step 1

Select your domain in the Cloudflare dashboard. In the left menu, go to Observability > Export > Logpush.
If your dashboard still shows the older menu, Logpush is under Analytics & Logs > Logpush.
Cloudflare left menu with Observability, Export, and Logpush selected
2

Step 2

Select Create a Logpush job. Under Select a destination, select HTTP destination.Cloudflare HTTP Destination
3

Step 3

Enter the API URL in the following format, with your Profound Log Ingestion Token, and select Continue.
4

Step 4

Select Filtered logs under If logs match…, then filter by the ClientRequestHost field to match your domain.
Use your own domain in the filter. www.tryprofound.com is only an example.
Cloudflare Filter Logs
5

Step 5

Select the HTTP requests dataset and choose the following fields to send. Agent Analytics skips a log line that is missing a required field. The other fields are optional.
  • Request
    • ClientIP (required) - IP address of the client.
    • ClientRequestHost (required) - Host requested by the client.
    • ClientRequestMethod (required) - HTTP method of client request.
    • ClientRequestReferer - HTTP request referrer.
    • ClientRequestURI (required) - URI requested by the client.
    • ClientRequestUserAgent (required) - User agent reported by the client.
  • Performance
    • EdgeStartTimestamp (required) - Timestamp at which the edge received request from the client.
    • EdgeEndTimestamp (required) - Timestamp at which the edge finished sending response to the client.
  • Response
    • EdgeResponseBytes - Number of bytes returned by the edge to the client.
    • EdgeResponseStatus - HTTP status code returned by Cloudflare to the client.
That’s it! You have now successfully configured Profound Agent Analytics for your website. Data should begin to populate on your dashboard within an hour.

Troubleshooting

  • If logs don’t appear, verify the Log Ingestion Token in the API URL.
  • Check the job status under Observability > Export > Logpush. Cloudflare shows the delivery health of each job there.
  • Ensure the ClientRequestHost filter matches the domain you registered in Profound.
  • Ensure the dataset is HTTP requests and that you selected every required field from Step 5. Agent Analytics skips a log line that is missing a required field.

Additional resources

Security considerations

  • Store Log Ingestion Tokens as secrets in production environments
  • Regularly rotate Log Ingestion Tokens
  • Monitor your Logpush job health for unusual patterns