fix(Whats new): Fixed builds errors

newrelic · Oct 24, 2024 · 5bfb727 · 5bfb727
1 parent ffd8164
commit 5bfb727
Showing 1 changed file with 14 additions and 31 deletions.
diff --git a/src/content/whats-new/2024/10/whats-new-10-23-kogs-gateway-logs-integration.md b/src/content/whats-new/2024/10/whats-new-10-23-kogs-gateway-logs-integration.md
@@ -3,7 +3,7 @@ title: 'Forward logs from Kong Gateway to New Relic'
 summary: 'Gain valuable insights into API gateway performance, health, security, and usage'
 releaseDate: '2024-10-26'
 learnMoreLink: 'https://docs.newrelic.com/docs/logs/forward-logs/kong-gateway/'
-getStartedLink: 'https://docs.newrelic.com/docs/logs/ui-data/use-logs-ui/’
+getStartedLink: 'https://docs.newrelic.com/docs/logs/ui-data/use-logs-ui/'
 ---
 
 Today’s IT organizations using Kong Gateway often struggle to gain comprehensive visibility into their API performance, health, and security which can lead to unexpected issues, downtime, and security vulnerabilities.
@@ -18,52 +18,35 @@ New Relic's integration with Kong Gateway, using the File Log plugin, provides a
 
 ## Forward Kong Gateway logs
 
-The File Log plugin for Kong Gateway enables the forwarding of logs to New Relic by directing them to standard output (/dev/stdout). This setup allows NewRelic’s Kubernetes logging plugin integration to collect and forward the logs.
+The File Log plugin for Kong Gateway enables the forwarding of logs to New Relic by directing them to standard output (`/dev/stdout`). This setup allows New Relic’s Kubernetes logging plugin integration to collect and forward the logs.
 
-## Configuration Setup
+## Configuration setup
 
 Follow these steps:
 
 **Step 1: Install the New Relic Kubernetes logging integration**
 
-Before configuring the File Log plugin, ensure you have the New Relic Kubernetes logging integration installed. Follow the [instructions](https:/docs.newrelic.com/docs/logs/forward-logs/kubernetes-plugin-log-forwarding/) to set this up.
+  Before configuring the File Log plugin, ensure you have the New Relic Kubernetes logging integration installed. Follow the [instructions](https:/docs.newrelic.com/docs/logs/forward-logs/kubernetes-plugin-log-forwarding/) to set this up.
 
 **Step 2: Install and configure Kong File Log plugin**
 
-Once the New Relic Logging Integration is installed, configure the File Log to output logs to `/dev/stdout` .  
-Here is an example manifest for enabling the File Log plugin:
-
- ```yaml
-        # file-log-plugin.yaml
-        apiVersion: configuration.konghq.com/v1
-        kind: KongClusterPlugin
-        metadata:
-            name: global-file-log
-            annotations:
-                kubernetes.io/ingress.class: kong
-            labels:
-                global: "true"
-        config:
-            path: "/dev/stdout" # Directs logs through a standard output so New Relic can receive Kong Gateway logs
-        plugin: file-log
-        ```
-
+Once the New Relic Logging Integration is installed, configure the File Log to output logs to `/dev/stdout` . See an example of the manifest configuration file in the [Configure the File Log plugin](https://docs.newrelic.com/docs/logs/forward-logs/kong-gateway/#install-config-filelog) section.
 
-**Step 3: Apply the Log File Log plugin Configuration**
+**Step 3: Apply the Log File Log plugin configuration**
 
-Deploy the File Log plugin configuration to your Kubernetes cluster using the following command:
+   * Deploy the File Log plugin configuration to your Kubernetes cluster using the following command:
 
-```bash
-  kubectl apply -f file-log-plugin.yaml -n kong
-```
+        ```bash
+        kubectl apply -f file-log-plugin.yaml -n kong
+        ```
 
-Replace `file-log-plugin.yaml` with the actual filename of your manifest.
+   * Replace `file-log-plugin.yaml` with the actual filename of your manifest.
 
-**Step 4 Verify the configuration:**
+**Step 4: Verify the configuration**
 
-After applying the configuration, verify that logs are being forwarded to New Relic by checking the [New Relic Logs UI](https://one.newrelic.com/launcher/logger.log-launcher) for entries from Kong Gateway.
+  After applying the configuration, verify that logs are being forwarded to New Relic by checking the [New Relic Logs UI](https://one.newrelic.com/launcher/logger.log-launcher) for entries from Kong Gateway.
 
-By forwarding Kong Gateway logs to New Relic, organizations can effectively monitor and manage their API gateways, ensuring optimal performance and security.
+  By forwarding Kong Gateway logs to New Relic, organizations can effectively monitor and manage their API gateways, ensuring optimal performance and security.
 
 ## To get started