Skip to content

Commit a06ffff

Browse files
Hyperlint Automation Fix
1 parent 03122a1 commit a06ffff

File tree

1 file changed

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

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ To configure Workers Logpush for AI Gateway, follow these steps:
3838

3939
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 and OpenSSL.
4040

41-
<Tabs syncKey="JSPlusSSL"> <TabItem label="Javascript">
41+
<Tabs syncKey="JSPlusSSL"> <TabItem label="JavaScript">
4242

4343
```js title="JavaScript"
4444
const crypto = require("crypto");
@@ -99,11 +99,11 @@ After configuring Workers Logpush, logs will be sent encrypted using the public
9999

100100
To decrypt the encrypted log bodies and metadata from AI Gateway, you can use the following Node.js script or OpenSSL:
101101

102-
<Tabs syncKey="JSPlusSSL"> <TabItem label="Javascript">
102+
<Tabs syncKey="JSPlusSSL"> <TabItem label="JavaScript">
103103

104104
To decrypt the encrypted log bodies and metadata from AI Gateway, download the logs to a folder, in this case its named `my_log.log.gz`.
105105

106-
Then copy this javascript file into the same folder and place your private key in the top variable.
106+
Then copy this JavaScript file into the same folder and place your private key in the top variable.
107107

108108
```js title="JavaScript"
109109
const privateKeyStr = `-----BEGIN RSA PRIVATE KEY-----

0 commit comments

Comments
 (0)