Skip to main content
This information is for Chronosphere Telemetry Pipeline, which is a standalone product separate from Chronosphere Observability Platform.
Requires pipeline agent v25.3.8 or later.
The Cloudflare LogPush source plugin (name: cloudflare) lets you ingest data from Cloudflare LogPush jobs into a telemetry pipeline. This is a push-based source plugin.
This plugin doesn’t support duplicates of itself within the same pipeline.

Supported telemetry types

The for Chronosphere Telemetry Pipeline supports these telemetry types:

Configuration parameters

Use the parameters in this section to configure the . The Telemetry Pipeline web interface uses the items in the Name column to describe these parameters. Pipeline configuration files use the items in the Key column as YAML keys.

General

Security and TLS

Ownership Challenge

Advanced

LogPush jobs

For information about setting up Cloudflare LogPush jobs, consult the Cloudflare LogPush Enable HTTP destination guide. When you create a new LogPush job in Cloudflare, there might be a delay before data from that job starts flowing to Telemetry Pipeline. Similarly, when you delete a LogPush job in Cloudflare, there might be a delay before data stops flowing. These delays can range anywhere from a few minutes to 15 minutes.

Ownership challenge

You can set Skip Ownership Challenge to false to trigger a one-time Cloudflare ownership challenge for enhanced security and safety. However, this ownership challenge is optional, and it’s possible to send LogPush data to Telemetry Pipeline without it.
If you trigger an ownership challenge outside of Telemetry Pipeline, the ensuing challenge response will appear in your pipeline logs, including tokens, and will be sent to any of your pipeline’s active destinations. This behavior occurs even when the Skip Ownership Challenge setting in Telemetry Pipeline is set to true.