# Cloudflare Log Push with qryn.cloud

## Cloudflare Logpush

**Cloudflare** can trace all your request or event logs to [qryn.cloud](https://qryn.cloud) using **Logpush**, which can be configured via the Cloudflare dashboard or API for paid accounts.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1678208130388/0fad7f5d-aa4c-4f88-8345-6d3afb3d8460.png align="center")

Using [qryn](https://qryn.cloud) as your **Logpush** endpoint is straightforward to set up and allows you to ingest, query and visualize all your **Cloudflare logs** in just seconds using the *Datadog compatible APIs* of our [polyglot observability stack](https://qryn.dev), proudly part of the first cohort of **startups** selected to participate the [**Cloudflare** Workers **Launchpad** program](https://blog.qryn.dev/cloudflare-workers-launchpad-qryn)!

### Requirements

* [Cloudflare](https://cloudflare.com) paid account
    
* [qryn.cloud](https://qryn.cloud) paid account or [free trial](https://qryn.cloud) on [gigapipe.com](https://gigapipe.com)
    

## Configuration

To set up Cloudflare's Logpush feature, navigate to your **Cloudflare dashboard**.

Find the **'Analytics & Logs'** Section.

Inside you will find **Logs**, which have recently been made available to any paid user of Cloudflare *(previously for Enterprise only)*, making it even easier to monitor **Workers, Firewalls, Gateway and Audit Logs** across all zones and regions.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1678202028076/28c9e991-dd60-4d05-b5f5-a36a37917551.png align="center")

Click '**Add Logpush Job**' and select the type of Logs you want to forward to [qryn](https://qryn.cloud)

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1678202093849/3f4d3891-279c-4674-9b80-72b8a0f86def.png align="center")

For this example, we will use **Workers Trace Events**, but any available dataset can be configured and used based on your specific needs.

Click '**Select**' and scroll to the bottom to click '**Next**'.

Cloudflare lets you select which types and frequency of events you want to monitor.

Check out the **"*Advanced Settings*"** at the bottom of the selector to activate and configure the desired sampling percentages.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1678203572425/c5a70f37-a7e2-406c-af51-f4cc3e5bacc1.png align="center")

Once you have all configured, click '**Next**' to proceed to the receiver selection.

Select the "**Datadog**" receiver and click '**Next**'.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1678292024111/bd7dcbfd-afea-4bcc-b7b9-93157d0b15fd.png align="center")

> ***💡*** Why Datadog? [qryn.cloud](https://qryn.cloud) is transparently compatible with Datadog ingestion.

### Datadog URL Endpoint

Add the destination information, based on your [qryn.cloud](https://qryn.cloud) account endpoint + the /cf/v1/insert path. This will make sure your data ends up in the right place.

> Example: **<mark>myaccount</mark>.qryn.cloud<mark>/cf/v1/insert</mark>**
> 
> IMPORTANT: Host + path only. DO NOT include the protocol (<s>https://</s>)

### Datadog API Key

Use [qryn.cloud](https://qryn.cloud) authentication **API-Key** and **Secret** separated by a semicolon *(:)*

> Example: **<mark>YOUR_API_KEY</mark>:<mark>YOUR_API_SECRET</mark>**

### Datadog ddsource field

The ddsource field will be converted into a label/tag. For example, using "<mark>cloudflare</mark>" will allow you to search using the Logql selector '***{ddsource="cloudflare"}*'**.

Once ready, click on the '**Validate access**' button to confirm the last page and you are all set to receive your Cloudflare logs with the rest of your observability data.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1678206363348/fb90b500-a776-4116-abb6-6566537ec72c.png align="center")

### Result

You can instantly **query** your **Cloudflare logs** using LogQL and the **Gigapipe Grafana** instance automatically provided and configured with each [qryn.cloud](https://qryn.cloud) account:

> {ddsource="cloudflare"}

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1678209595876/26a84aca-e64a-4dda-9214-8da32adbb908.png align="center")

---

### Alternatives

💡 Prefer using your own Cloudflare **Workers** to handle Logpush inserts qryn.cloud or qryn.dev using LogQL? [Here's how](https://github.com/metrico/cloudflare-worker-logpush-loki/tree/qryn) 👈

💡 How about sending our logs and telemetry directly from our Apps without adding tons of dependencies and libraries? Check out [Boscaiolog](https://blog.qryn.dev/client-logs-from-anywhere) 👈

---

### Conclusion

Just a few clicks and you are all set, ready to gain full observability over your Cloudflare **Workers, Firewalls, Gateway and Audit Logs** across all zones and regions alongside the rest of your observability data, instantly available through the power of **LogQL** and [qryn](https://qryn.cloud) on top of **ClickHouse** and its columnar superpowers.

*Next: add Logs, Metrics and Traces for end-to-end visibility using qryn's polyglot API to ingest Loki, Prometheus, Opentelemetry, InfluxDB, Elastic and many more formats.*

[![](https://cdn.hashnode.com/res/hashnode/image/upload/v1676413342775/491ef8fb-6764-4786-8d87-02d3a0e60642.png?auto=compress,format&format=webp align="center")](https://qryn.cloud)