Skip to content

Update logpush.mdx #17890

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 31, 2024
Merged

Update logpush.mdx #17890

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9e12719
Update logpush.mdx
kathayl Oct 30, 2024
51382c5
Update limits.mdx
kathayl Oct 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion src/content/docs/ai-gateway/observability/logging/logpush.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,14 +13,16 @@ You can toggle Logpush on and off in the [Cloudflare dashboard](https://dash.clo

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.

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.
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.

:::note[Note]

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

:::

<Render file="limits-increase" product="ai-gateway" />

## How logs are encrypted

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.
Expand Down
15 changes: 8 additions & 7 deletions src/content/docs/ai-gateway/reference/limits.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,13 +11,14 @@ The following limits apply to gateway configurations, logs, and related features

| Feature | Limit |
| --------------------------------------------------------------- | ----------------------------------- |
| Maximum datasets | 10 per gateway |
| Maximum gateways | 10 per account |
| Maximum logs stored [paid plan](/ai-gateway/reference/pricing/) | 10 million per gateway <sup>1</sup> |
| Maximum logs stored [free plan](/ai-gateway/reference/pricing/) | 100,000 per account <sup>2</sup> |
| Maximum log size stored | 10 MB per log <sup>3</sup> |
| Maximum Logpush jobs | 4 per account |
| Maximum gateway name length | 64 characters |
| Datasets | 10 per gateway |
| Gateways | 10 per account |
| Logs stored [paid plan](/ai-gateway/reference/pricing/) | 10 million per gateway <sup>1</sup> |
| Logs stored [free plan](/ai-gateway/reference/pricing/) | 100,000 per account <sup>2</sup> |
| Log size stored | 10 MB per log <sup>3</sup> |
| Logpush jobs | 4 per account |
| Logpush size limit | 1MB per log |
| Gateway name length | 64 characters |

<sup>1</sup> If you have reached 10 million logs stored per gateway, new logs
will stop being saved. To continue saving logs, you must delete older logs in
Expand Down
Loading