Skip to content

Commit 9e12719

Browse files
authored
Update logpush.mdx
add logpush size limit of 1MB per log
1 parent ee332ed commit 9e12719

File tree

1 file changed

+3
-1
lines changed
  • src/content/docs/ai-gateway/observability/logging

1 file changed

+3
-1
lines changed

src/content/docs/ai-gateway/observability/logging/logpush.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,14 +13,16 @@ You can toggle Logpush on and off in the [Cloudflare dashboard](https://dash.clo
1313

1414
This guide explains how to set up Logpush for AI Gateway, generate an RSA key pair for encryption, and decrypt the logs once they are received.
1515

16-
You can store up to 10 million logs per gateway. If your limit is reached, new logs will stop being saved and will not be exported through Logpush. To continue saving and exporting logs, you must delete older logs to free up space for new logs. Logpush has a limit of 4 jobs.
16+
You can store up to 10 million logs per gateway. If your limit is reached, new logs will stop being saved and will not be exported through Logpush. To continue saving and exporting logs, you must delete older logs to free up space for new logs. Logpush has a limit of 4 jobs and a maximum request size of 1 MB per log.
1717

1818
:::note[Note]
1919

2020
To export logs using Logpush, you must have logs turned on for the gateway.
2121

2222
:::
2323

24+
<Render file="limits-increase" product="ai-gateway" />
25+
2426
## How logs are encrypted
2527

2628
We employ a hybrid encryption model efficiency and security. Initially, an AES key is generated for each log. This AES key is what actually encrypts the bulk of your data, chosen for its speed and security in handling large datasets efficiently.

0 commit comments

Comments
 (0)