Skip to content

Commit 96886b1

Browse files
jsells1caley-b
andauthored
[Log Explorer] Add pricing and managing usage page (#29105)
* [Log Explorer] Add pricing and managing usage page * Update src/content/docs/log-explorer/pricing.mdx --------- Co-authored-by: Caley Burton <caley@cloudflare.com>
1 parent 0a491ff commit 96886b1

File tree

1 file changed

+96
-0
lines changed

1 file changed

+96
-0
lines changed
Lines changed: 96 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
1+
---
2+
title: Pricing and managing usage
3+
pcx_content_type: concept
4+
sidebar:
5+
order: 5
6+
---
7+
8+
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.
9+
10+
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.
11+
12+
## Availability
13+
14+
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.
15+
16+
## Billable usage
17+
18+
Log Explorer billing is strictly consumption-based, calculated by the GBs ingested and stored.
19+
20+
### Attack traffic
21+
22+
Because Log Explorer is a forensics product, attack traffic is considered valuable data for analysis and is included in your billable usage.
23+
24+
:::note
25+
Logs generated from Layer 7 (L7) DDoS attack traffic are not ingested by default and do not count toward your Log Explorer usage.
26+
:::
27+
28+
## Estimate usage
29+
30+
To estimate your Log Explorer usage, review your request volumes in **Analytics** for specific Cloudflare log datasets.
31+
32+
### Record size by dataset
33+
34+
The following table provides average and maximum record sizes for each dataset to help you estimate potential storage needs:
35+
36+
| Dataset | Average Record Size | Maximum Record Size |
37+
| ----------------------------- | ------------------- | ------------------- |
38+
| `audit_logs` | 2.69 kB | 172 kB |
39+
| `email_security_alerts` | 6.74 kB | 74.9 kB |
40+
| `firewall_events` | 1.36 kB | 47.2 kB |
41+
| `audit_logs_v2` | 1.73 kB | 28.5 kB |
42+
| `zaraz_events` | 7.30 kB | 11.7 kB |
43+
| `http_requests` | 1.56 kB | 9.76 kB |
44+
| `gateway_dns` | 1.44 kB | 6.23 kB |
45+
| `dex_application_tests` | 3.29 kB | 5.67 kB |
46+
| `casb_findings` | 2.67 kB | 3.80 kB |
47+
| `gateway_http` | 1.47 kB | 2.60 kB |
48+
| `dex_device_state_events` | 1.98 kB | 2.57 kB |
49+
| `page_shield_events` | 443 B | 2.02 kB |
50+
| `network_analytics_logs` | 1.31 kB | 1.87 kB |
51+
| `zero_trust_network_sessions` | 1.21 kB | 1.52 kB |
52+
| `gateway_network` | 877 B | 1.17 kB |
53+
| `device_posture_results` | 730 B | 944 B |
54+
| `spectrum_events` | 685 B | 925 B |
55+
| `sinkhole_http_logs` | 705 B | 705 B |
56+
| `access_requests` | 446 B | 541 B |
57+
| `dns_firewall_logs` | 387 B | 469 B |
58+
| `dns_logs` | 199 B | 409 B |
59+
| `magic_ids_detections` | 334 B | 349 B |
60+
| `warp_toggle_changes` | 327 B | 335 B |
61+
| `ipsec_logs` | 207 B | 260 B |
62+
| `nel_reports` | 204 B | 224 B |
63+
64+
## Monitor usage
65+
66+
Cloudflare provides three primary ways to track your consumption and maintain financial oversight:
67+
68+
- **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.
69+
- **Account-level billing**: Access a detailed view of current and previous months' cumulative usage under **Manage Account** > **Billing**.
70+
- **Usage alerts**: Set up automated notifications to trigger when billable usage exceeds a defined threshold.
71+
72+
### Configure a usage alert
73+
74+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select **Manage account**.
75+
2. Go to **Notifications** > **Add**.
76+
3. Select **Usage-based Billing**.
77+
4. Define your threshold and the notification destination (email, PagerDuty, or webhooks).
78+
79+
## Deactivate Log Explorer
80+
81+
To stop using Log Explorer and end associated charges, you must complete both of the following steps:
82+
83+
### 1. Stop log ingestion
84+
85+
Disabling datasets stops additional ingestion charges immediately.
86+
87+
1. Go to the [Manage datasets](https://dash.cloudflare.com/?to=/:account/log-explorer/manage-sources) page at the account level.
88+
2. Use the toggle to turn off each dataset you no longer need.
89+
3. Select **Stop ingesting logs** to confirm.
90+
91+
### 2. Cancel the subscription
92+
93+
This prevents the subscription from renewing at the next billing cycle.
94+
95+
1. Go to the [Billing](https://dash.cloudflare.com/?to=/:account/billing) page.
96+
2. In the **Subscriptions** tab, find the **Log Explorer** subscription and select **Cancel**.

0 commit comments

Comments
 (0)