From d2967c4b6b906849590f7f1d04e5fc7ae8084731 Mon Sep 17 00:00:00 2001 From: Sohei Gallagher Date: Fri, 7 Feb 2025 17:51:48 -0800 Subject: [PATCH] [Logs] Remove Max Upload Parameters limitation note for Edge Log Delivery This removes Max Upload Parameters limitation note for Edge Log Delivery, as they are now supported. --- src/content/docs/logs/get-started/api-configuration.mdx | 5 ----- 1 file changed, 5 deletions(-) diff --git a/src/content/docs/logs/get-started/api-configuration.mdx b/src/content/docs/logs/get-started/api-configuration.mdx index 52aebf9ca084b67..8631d966867624c 100644 --- a/src/content/docs/logs/get-started/api-configuration.mdx +++ b/src/content/docs/logs/get-started/api-configuration.mdx @@ -257,11 +257,6 @@ These parameters can be used to gain control of batch size in the case that a de 2. **max\_upload\_records** (optional): The maximum number of log lines per batch. This setting must be between 1,000 and 1,000,000 lines. Note that you cannot specify a minimum number of log lines per batch; this means that log files may contain many fewer lines than this. 3. **max\_upload\_interval\_seconds** (optional): The maximum interval in seconds for log batches. This setting must be between 30 and 300 seconds. Note that you cannot specify a minimum interval for log batches; this means that log files may be sent in shorter intervals than this. -:::note[Note] - -Parameters **max\_upload\_bytes** and **max\_upload\_records** are not configurable for Edge Log Delivery. -::: - ## Custom fields You can add custom fields to your HTTP request log entries in the form of HTTP request headers, HTTP response headers, and cookies. Custom fields configuration applies to all the Logpush jobs in a zone that use the HTTP requests dataset. To learn more, refer to [Custom fields](/logs/reference/custom-fields/).