Moves faq to a new page and adds faq about log volume.

Author: angelampcosta

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

@@ -0,0 +1,37 @@
+---
+pcx_content_type: faq
+title: FAQ
+structured_data: true
+description: Find answers to common questions about Log Explorer.
+sidebar:
+  order: 152
+---
+
+### Which fields (or columns) are available for querying?
+
+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. 
+
+### Why does my query not complete or time out?
+
+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.
+
+### Why don't I see any logs in my queries after enabling the dataset?
+
+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.
+
+### My query returned an error. How do I figure out what went wrong?
+
+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), make sure you have included a date and a limit. If the query still fails it is likely timing out. Try refining your filters.
+
+### Where is the data stored?
+
+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.
+
+### Does Log Explorer support Customer Metadata Boundary?
+
+Customer metadata boundary is currently not supported for Log Explorer.
+
+### Are there any constraints on the log volume that Log Explorer can support?
+
+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.
+

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

@@ -114,30 +114,4 @@ WHERE
 
 - Narrow your query time frame. Focus on a smaller time window to reduce the volume of data processed. This helps avoid querying excessive amounts of data and speeds up response times.
 - Omit `ORDER BY` and `LIMIT` clauses. These clauses can slow down queries, especially when dealing with large datasets. For queries that return a large number of records, reduce the time frame instead of limiting to the newest `N` records from a broader time frame.
-- Select only necessary columns. For example, replace `SELECT *` with the list of specific columns you need. You can also use `SELECT RayId` as a first iteration and follow up with a query that filters by the Ray IDs to retrieve additional columns. Additionally, you can use `SELECT COUNT(*)` to probe for time frames with matching records without retrieving the full dataset.
-
-## FAQs
-
-### Which fields (or columns) are available for querying?
-
-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. 
-
-### Why does my query not complete or time out?
-
-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.
-
-### Why don't I see any logs in my queries after enabling the dataset?
-
-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.
-
-### My query returned an error. How do I figure out what went wrong?
-
-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), make sure you have included a date and a limit. If the query still fails it is likely timing out. Try refining your filters.
-
-### Where is the data stored?
-
-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.
-
-### Does Log Explorer support Customer Metadata Boundary?
-
-Customer metadata boundary is currently not supported for Log Explorer.
+- Select only necessary columns. For example, replace `SELECT *` with the list of specific columns you need. You can also use `SELECT RayId` as a first iteration and follow up with a query that filters by the Ray IDs to retrieve additional columns. Additionally, you can use `SELECT COUNT(*)` to probe for time frames with matching records without retrieving the full dataset.