Skip to main content

Cloudflare Logpush

Receives logs pushed from Cloudflare via the Logpush HTTP destination. Cloudflare Logpush delivers logs as gzipped NDJSON to a configured HTTP endpoint, enabling real-time ingestion of Cloudflare datasets into Monad pipelines.

Sync Type: Streaming

Requirements​

  • A Cloudflare account with Logpush access (Enterprise plan or specific add-ons depending on the dataset)
  • A Monad pipeline configured with the Cloudflare Logpush input

Setup​

1. Create a Monad Pipeline​

  1. In the Monad UI, create a new pipeline
  2. Select Cloudflare Logpush as the input type
  3. Save the pipeline and note the HTTP endpoint URL provided

2. Configure Cloudflare Logpush​

  1. Log in to your Cloudflare dashboard
  2. Navigate to Analytics & Logs > Logpush
  3. Click Create a Logpush job
  4. Select the dataset you want to push (e.g., HTTP requests, Firewall events, DNS logs)
  5. Choose HTTP as the destination
  6. Enter the Monad HTTP endpoint URL as the destination URL
  7. Add authentication headers as required by your Monad API configuration
  8. Configure any filters or fields as needed
  9. Save and enable the Logpush job

Details​

  • Delivery Format: Cloudflare delivers logs as gzipped NDJSON (newline-delimited JSON). Monad automatically decompresses and splits the payload into individual records.
  • Push Frequency: Cloudflare pushes logs in batches, typically every 30 seconds to 5 minutes depending on log volume and configuration.
  • Available Datasets: HTTP requests, Firewall events, DNS logs, Spectrum events, NEL reports, Access requests, Gateway DNS/HTTP/Network logs, Audit logs, Workers Trace events, and more.
  • No Polling: Unlike other Cloudflare inputs, Logpush is push-based — Cloudflare sends data to Monad rather than Monad fetching it.

Configuration​

No additional settings or secrets are required for this input. Authentication is handled via the Monad API key included in the Logpush destination URL or headers.

Troubleshooting​

Common Issues​

Issue: Logpush job shows errors or fails to deliver logs Cause: The destination URL may be incorrect or unreachable from Cloudflare. Solution: Verify the Monad HTTP endpoint URL is correct and accessible. Check that your Monad pipeline is active and running.

Issue: Authentication failures in Logpush job status Cause: The API key or authentication headers are missing or incorrect. Solution: Ensure the correct Monad API key is included in the Logpush destination configuration, either in the URL or as an authentication header.

Issue: Logs are delivered but not appearing in the pipeline Cause: The Logpush job may be configured but the pipeline is not active, or filters are excluding all records. Solution: Confirm the Monad pipeline is running and check the Logpush job filters in the Cloudflare dashboard.

Issue: Partial or malformed records Cause: Network interruptions during log delivery can result in incomplete payloads. Solution: Cloudflare automatically retries failed deliveries. If the issue persists, check for network connectivity between Cloudflare and your Monad endpoint.