The Activity log allows you to see individual DNS queries made from your locations or, for paid subscribers, HTTP requests made from WARP clients. You can use the Activity log to investigate anomalies in your network. You can search by the DNS query or HTTP request and investigate each by clicking on a row.
When you click on the row, you can see information related to the identity that is making the DNS request and attributes relevant to the DNS queries.
Explanation of the fields
Explanation of the fields
|Host||The hostname in the HTTP header for the HTTP request.|
|Method||The HTTP method used for the request (e.g., GET, POST, etc.)|
|Decision||The Gateway action taken based on the first rule that matched. For example: Allowed, Blocked, Bypass, etc.|
|Time||The timestamp of the HTTP request|
|URL||The full URL of the HTTP request|
|Device||The ID of the device that made the request. This is generated by the WARP client on the device that created the request.|
|Referer||The Referer request header contains the address of the page making the request.|
|User Agent||The user agent header sent in the request by the originating device.|
|File Name||File name string if a file transfer occurred or was attempted.|
|HTTP version||The HTTP version of the origin that Gateway connected to on behalf of the user.|
|Policy details||The policy corresponding to the decision Gateway made based on the traffic criteria of the request.|
When a user creates a policy to isolate traffic, the initial request that triggers isolation will be logged as an
Isolate decision and the
is_isolated field will return
false. This is because that initial request is not isolated yet — but it initiates an isolated session.
Since the request is generated in an isolated browser, the result is rendered in the isolated browser and rendered back to the user securely. This request and all subsequent requests in the isolated browser are logged to include the terminal Gateway action that gets applied (e.g. Allow / Block) and the
is_isolated field as
Cloudflare logpush integration
You can configure the automatic export of logs from Cloudflare Gateway to third-party storage destinations or to security information and event management (SIEM) tools. Once exported, your team can analyze and audit the data as needed. This feature builds on Cloudflare's Logpush Service. To enable this feature on the Teams dashboard:
- Navigate to Logs > Logpush.
- Click Connect a service.
- Enter a Job name.
- From the drop-down menu, choose whether to export the Gateway DNS or the Gateway HTTP dataset.
- Next, select the data fields you want to export.
- In the Advanced settings card, choose the timestamp format you prefer, and whether you want to enable logs sampling.
- Click Next.
- Select the service you want to export your Gateway logs to.
- Next, follow the service-specific instructions on the Teams UI to validate your destination.
The setup of your logpush integration is now complete. Logpush will send updated logs every five minutes to your selected destination.
You can configure multiple destinations and monitor for any issues by returning to the Logpush page.