You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/ai-gateway/observability/logpush.mdx
+13-10Lines changed: 13 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,13 +12,12 @@ AI Gateway allows you to securely export logs to an external storage location, w
12
12
You can toggle Logpush on and off in the [Cloudflare dashboard](https://dash.cloudflare.com) settings.
13
13
14
14
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.
15
-
Logpush has a limit of 4 jobs. If you have reached the [limit of logs stored for your plan](/ai-gateway/reference/limits/), logs will not be exported through Logpush.
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.
18
17
19
18
:::note[Note]
20
19
21
-
To export logs using Logpush, you must have logs turned on for the gateway or have overridden the gateway settings by using the `cf-aig-collect-log` request header.
20
+
To export logs using Logpush, you must have logs turned on for the gateway.
22
21
23
22
:::
24
23
@@ -59,19 +58,17 @@ This script will output your RSA privateKey and publicKey on your terminal. Keep
59
58
60
59
## 2. Upload public key to gateway settings
61
60
62
-
Once you have generated the key pair, upload the public key to your AI Gateway settings. This key will be used to encrypt your logs. For more information on Logpush refer to [Logs](/logs/get-started/).
61
+
Once you have generated the key pair, upload the public key to your AI Gateway settings. This key will be used to encrypt your logs. In order to enable Logpush, you will need logs enabled for that gateway.
63
62
64
-
:::note[Note]
65
-
You should enable Logpush in AI Gateway settings. This option only shows up when logs are enabled.
66
-
You can toggle on or off as needed. If you do not have logs turned on nothing will be saved.
63
+
## 3. Set up Logpush
67
64
68
-
:::
65
+
To set up Logpush, refer to [Logpush Get Started](/logs/get-started/).
69
66
70
-
## 3. Receive encrypted logs
67
+
## 4. Receive encrypted logs
71
68
72
69
After configuring Logpush, logs will be sent encrypted using the public key you uploaded. To access the data, you will need to decrypt it using your private key. The logs will be sent to the object storage provider that you have selected.
73
70
74
-
## 4. Decrypting logs
71
+
## 5. Decrypting logs
75
72
76
73
To decrypt the encrypted log bodies and metadata from AI Gateway, you can use the following Node.js script:
0 commit comments