-
Notifications
You must be signed in to change notification settings - Fork 13.2k
[Log Explorer] Add pricing and managing usage page #29105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
caley-b
merged 2 commits into
cloudflare:production
from
jsells1:log-explorer/pricing-page
Mar 18, 2026
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,96 @@ | ||
| --- | ||
| title: Pricing and managing usage | ||
| pcx_content_type: concept | ||
| sidebar: | ||
| order: 5 | ||
| --- | ||
|
|
||
| Log Explorer billing is based on the volume of logs ingested and stored, measured in gigabytes (GB). Your charges scale with the amount of log data you choose to retain in Log Explorer. | ||
|
|
||
| Unlike query-based billing models, charges are not based on how often you search or scan your data. Once logs are ingested and stored, you can query them without additional cost. | ||
|
|
||
| ## Availability | ||
|
|
||
| Log Explorer is available as a paid add-on for any Application Services or Zero Trust purchase. There is no free version or trial available at this time. | ||
|
|
||
| ## Billable usage | ||
|
|
||
| Log Explorer billing is strictly consumption-based, calculated by the GBs ingested and stored. | ||
|
|
||
| ### Attack traffic | ||
|
|
||
| Because Log Explorer is a forensics product, attack traffic is considered valuable data for analysis and is included in your billable usage. | ||
|
|
||
| :::note | ||
| Logs generated from Layer 7 (L7) DDoS attack traffic are not ingested by default and do not count toward your Log Explorer usage. | ||
| ::: | ||
|
|
||
| ## Estimate usage | ||
|
|
||
| To estimate your Log Explorer usage, review your request volumes in **Analytics** for specific Cloudflare log datasets. | ||
|
|
||
| ### Record size by dataset | ||
|
|
||
| The following table provides average and maximum record sizes for each dataset to help you estimate potential storage needs: | ||
|
|
||
| | Dataset | Average Record Size | Maximum Record Size | | ||
| | ----------------------------- | ------------------- | ------------------- | | ||
| | `audit_logs` | 2.69 kB | 172 kB | | ||
| | `email_security_alerts` | 6.74 kB | 74.9 kB | | ||
| | `firewall_events` | 1.36 kB | 47.2 kB | | ||
| | `audit_logs_v2` | 1.73 kB | 28.5 kB | | ||
| | `zaraz_events` | 7.30 kB | 11.7 kB | | ||
| | `http_requests` | 1.56 kB | 9.76 kB | | ||
| | `gateway_dns` | 1.44 kB | 6.23 kB | | ||
| | `dex_application_tests` | 3.29 kB | 5.67 kB | | ||
| | `casb_findings` | 2.67 kB | 3.80 kB | | ||
| | `gateway_http` | 1.47 kB | 2.60 kB | | ||
| | `dex_device_state_events` | 1.98 kB | 2.57 kB | | ||
| | `page_shield_events` | 443 B | 2.02 kB | | ||
| | `network_analytics_logs` | 1.31 kB | 1.87 kB | | ||
| | `zero_trust_network_sessions` | 1.21 kB | 1.52 kB | | ||
| | `gateway_network` | 877 B | 1.17 kB | | ||
| | `device_posture_results` | 730 B | 944 B | | ||
| | `spectrum_events` | 685 B | 925 B | | ||
| | `sinkhole_http_logs` | 705 B | 705 B | | ||
| | `access_requests` | 446 B | 541 B | | ||
| | `dns_firewall_logs` | 387 B | 469 B | | ||
| | `dns_logs` | 199 B | 409 B | | ||
| | `magic_ids_detections` | 334 B | 349 B | | ||
| | `warp_toggle_changes` | 327 B | 335 B | | ||
| | `ipsec_logs` | 207 B | 260 B | | ||
| | `nel_reports` | 204 B | 224 B | | ||
|
|
||
| ## Monitor usage | ||
|
|
||
| Cloudflare provides three primary ways to track your consumption and maintain financial oversight: | ||
|
|
||
| - **In-product quick indicator**: View your current month's usage directly within the Log Explorer interface at the top of the **Log Search** and **Manage Datasets** sections. | ||
| - **Account-level billing**: Access a detailed view of current and previous months' cumulative usage under **Manage Account** > **Billing**. | ||
| - **Usage alerts**: Set up automated notifications to trigger when billable usage exceeds a defined threshold. | ||
|
|
||
| ### Configure a usage alert | ||
|
|
||
| 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/). | ||
| 2. Go to **Notifications** > **Add**. | ||
| 3. Select **Usage-based Billing**. | ||
| 4. Define your threshold and the notification destination (email, PagerDuty, or webhooks). | ||
|
|
||
| ## Deactivate Log Explorer | ||
|
|
||
| To stop using Log Explorer and end associated charges, you must complete both of the following steps: | ||
|
|
||
| ### 1. Stop log ingestion | ||
|
|
||
| Disabling datasets stops additional ingestion charges immediately. | ||
|
|
||
| 1. Go to the [Manage datasets](https://dash.cloudflare.com/?to=/:account/log-explorer/manage-sources) page at the account level. | ||
| 2. Use the toggle to turn off each dataset you no longer need. | ||
| 3. Select **Stop ingesting logs** to confirm. | ||
|
|
||
| ### 2. Cancel the subscription | ||
|
|
||
| This prevents the subscription from renewing at the next billing cycle. | ||
|
|
||
| 1. Go to the [Billing](https://dash.cloudflare.com/?to=/:account/billing) page. | ||
| 2. In the **Subscriptions** tab, find the **Log Explorer** subscription and select **Cancel**. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.