Skip to content

Commit 8452217

Browse files
committed
Updates Log Explorer FAQ
1 parent 732159e commit 8452217

File tree

2 files changed

+23
-9
lines changed

2 files changed

+23
-9
lines changed
97.3 KB
Loading

src/content/docs/log-explorer/faq.mdx

Lines changed: 23 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -7,31 +7,31 @@ sidebar:
77
order: 152
88
---
99

10-
### Which fields (or columns) are available for querying?
10+
## Which fields (or columns) are available for querying?
1111

1212
All fields listed in [Datasets](/logs/logpush/logpush-job/datasets/) for the [supported datasets](/log-explorer/manage-datasets/#supported-datasets) are viewable in Log Explorer.
1313

14-
### Why does my query not complete or time out?
14+
## Why does my query not complete or time out?
1515

1616
Log Explorer performs best when query parameters focus on narrower ranges of time. You may experience query timeouts when your query would return a large quantity of data. Consider refining your query to improve performance.
1717

18-
### Why do I not see any logs in my queries after enabling the dataset?
18+
## Why do I not see any logs in my queries after enabling the dataset?
1919

2020
Log Explorer starts ingesting logs from the moment you enable the dataset. It will not display logs for events that occurred before the dataset was enabled. Make sure that new events have been generated since enabling the dataset, and check again.
2121

22-
### My query returned an error. How do I figure out what went wrong?
22+
## My query returned an error. How do I figure out what went wrong?
2323

2424
We are actively working on improving error codes. If you receive a generic error, check your SQL syntax (if you are using the custom SQL feature), and make sure you have included a date and a limit. If the query still fails it is likely timing out. Try refining your filters.
2525

26-
### Where is the data stored?
26+
## Where is the data stored?
2727

2828
The data is stored in Cloudflare R2. Each Log Explorer dataset is stored on a per-customer level, similar to Cloudflare D1, ensuring that your data is kept separate from that of other customers. In the future, this single-tenant storage model will provide you with the flexibility to create your own retention policies and decide in which regions you want to store your data.
2929

30-
### Does Log Explorer support Customer Metadata Boundary?
30+
## Does Log Explorer support Customer Metadata Boundary?
3131

3232
Customer Metadata Boundary is currently not supported for Log Explorer.
3333

34-
### Are there any constraints on the log volume that Log Explorer can support?
34+
## Are there any constraints on the log volume that Log Explorer can support?
3535

3636
We are continually scaling the Log Explorer data platform. At present, Log Explorer supports log ingestion rates of up to 50,000 records per second. If your needs exceed this, contact your account team.
3737

@@ -49,12 +49,26 @@ Log Explorer billing is based on the volume of logs indexed and stored, measured
4949

5050
## Are logs from attack traffic included in my Log Explorer usage?
5151

52-
Yes. Log Explorer bills are based on the total volume of logs ingested and stored, including attack traffic. Since these logs are often critical for investigating security incidents, they are treated the same as all other log data.
52+
Yes. In general, Log Explorer bills based on the total volume of logs ingested and stored, including attack traffic. Since these logs are often critical for investigating security incidents, they are treated the same as all other log data.
53+
54+
However, logs generated from Layer 7 (L7) DDoS attack traffic are not ingested by default and therefore do not count toward your Log Explorer usage.
5355

5456
## How does Log Explorer store data in R2, and why do I not see it in my own R2 bucket?
5557

5658
Log Explorer uses Cloudflare Logpush and R2 behind the scenes to stream and store logs. For technical and performance reasons, the data is stored in internal, customer-specific R2 buckets managed by Cloudflare. These buckets are single-tenant to keep your data isolated, but they are not visible in your account's R2 interface. You are not billed separately for this storage — it is included in your Log Explorer usage.
5759

5860
## Are Custom Dashboards based on R2 Log Explorer data, or on GraphQL?
5961

60-
Custom Dashboards currently run on GraphQL. Over time, this will evolve to include deeper integration between the two features, such as building charts directly from logs.
62+
Custom Dashboards currently run on GraphQL. Over time, this will evolve to include deeper integration between the two features, such as building charts directly from logs.
63+
64+
## How can I track my Log Explorer usage?
65+
66+
Your monthly usage is displayed at the top of the Log Search and Manage Datasets dashboard sections within Log Explorer.
67+
68+
![Usage display in the dashboard](~/assets/images/log-explorer/log-explorer-usage.png)
69+
70+
## How do I turn off Log Explorer?
71+
72+
Use the Manage Datasets feature to enable or disable ingestion for individual datasets and zones.
73+
74+
To cancel your self-serve subscription, go to **Manage Account** > **Billing** > **Subscriptions**, find the Log Explorer subscription, and select **Cancel**.

0 commit comments

Comments
 (0)