Logpush
BetaAI Gateway allows you to securely export logs to an external storage location, where you can decrypt and process them. You can toggle Logpush on and off in the Cloudflare dashboard ↗ settings.
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.
To configure Logpush for AI Gateway, follow these steps:
You need to generate a key pair to encrypt and decrypt the logs. This script will output your RSA privateKey and publicKey. Keep the private key secure, as it will be used to decrypt the logs. Below is a sample script to generate the keys using Node.js.
Run the script by executing the below code on your terminal. Replace file name
with the name of your JavaScript file.
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.
To set up Logpush, refer to Logpush Get Started.
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.
To decrypt the encrypted log bodies and metadata from AI Gateway, you can use the following Node.js script:
Run the script by executing the below code on your terminal. Replace file name
with the name of your JavaScript file.
The script reads the encrypted log file (my_log.log.gz)
, decrypts the metadata, request body, and response body, and prints the decrypted data.
Ensure you replace the privateKey
variable with your actual private RSA key that you generated in step 1.