Skip to content

Commit

Permalink
fix(Whats new): Fixed build errors
Browse files Browse the repository at this point in the history
  • Loading branch information
@nbaenam
nbaenam committed Oct 24, 2024
1 parent bde38d6 commit 96c1ecc
Showing 1 changed file with 27 additions and 24 deletions.
51 changes: 27 additions & 24 deletions src/content/whats-new/2024/10/Whats-new-10-23-Kogs Gateway Logs Integration.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,26 +6,31 @@ learnMoreLink: 'https://docs.newrelic.com/docs/logs/forward-logs/kong-gateway/'
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.
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.
New Relic's integration with Kong Gateway, using the File Log plugin, provides a robust solution for:
- **Centralized logging:** Kong Gateway logs are instantly contextualized with other application and telemetry data for a unified view.
- **Enhanced visibility:** Gain deeper insights into API gateway performance, health, and security.
- **Proactive issue detection:** Identify and address potential problems before they impact users.
- **Improved security:** Monitor for security threats and anomalies.
- **Optimized performance:** Identify and resolve performance bottlenecks before they impact uyser experience.

- **Centralized logging**: Kong Gateway logs are instantly contextualized with other application and telemetry data for a unified view.
- **Enhanced visibility**: Gain deeper insights into API gateway performance, health, and security.
- **Proactive issue detection**: Identify and address potential problems before they impact users.
- **Improved security**: Monitor for security threats and anomalies.

Check warning on line 16 in src/content/whats-new/2024/10/Whats-new-10-23-Kogs Gateway Logs Integration.md

View workflow job for this annotation

GitHub Actions / vale-linter 

[vale] reported by reviewdog 🐶
[new-relic.ComplexWords] Consider using 'check' or 'watch' instead of 'Monitor'.

Raw Output:
{"message": "[new-relic.ComplexWords] Consider using 'check' or 'watch' instead of 'Monitor'.", "location": {"path": "src/content/whats-new/2024/10/Whats-new-10-23-Kogs Gateway Logs Integration.md", "range": {"start": {"line": 16, "column": 26}}}, "severity": "INFO"}
- **Optimized performance**: Identify and resolve performance bottlenecks before they impact uyser experience.

## 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 NewRelic’s Kubernetes logging plugin integration to collect and forward the logs.

## Configuration Setup

Follow these steps:

# Configuration Setup:
**Step 1: Install the New Relic Kubernetes logging integration**

**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](/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` .
**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` .

Check warning on line 33 in src/content/whats-new/2024/10/Whats-new-10-23-Kogs Gateway Logs Integration.md

View workflow job for this annotation

GitHub Actions / vale-linter 

[vale] reported by reviewdog 🐶
[Microsoft.Passive] 'is installed' looks like passive voice.

Raw Output:
{"message": "[Microsoft.Passive] 'is installed' looks like passive voice.", "location": {"path": "src/content/whats-new/2024/10/Whats-new-10-23-Kogs Gateway Logs Integration.md", "range": {"start": {"line": 33, "column": 40}}}, "severity": "INFO"}
Here is an example manifest for enabling the File Log plugin:

```yaml
Expand All @@ -44,28 +49,26 @@ Here is an example manifest for enabling the File Log plugin:
```


**Step 3:** Apply the Log File Log plugin Configuration
Deploy the File Log plugin configuration to your Kubenrnetes cluster using the following command:
**Step 3: Apply the Log File Log plugin Configuration**

Deploy the File Log plugin configuration to your Kubernetes cluster using the following command:

```bash
kubectl apply -f file-log-plugin.yaml -n kong
kubectl apply -f file-log-plugin.yaml -n kong
```
Replace `file-log-plugin.yaml` with the actual filename of your manifest

**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
Replace `file-log-plugin.yaml` with the actual filename of your manifest.

**Step 4 Verify the configuration:**

By forwarding Kong Gateway logs to New Relic, organizations can effectively monitor and manage their API gateways,ensuring optimal performance and security.
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.

Check warning on line 64 in src/content/whats-new/2024/10/Whats-new-10-23-Kogs Gateway Logs Integration.md

View workflow job for this annotation

GitHub Actions / vale-linter 

[vale] reported by reviewdog 🐶
[Microsoft.Passive] 'being forwarded' looks like passive voice.

Raw Output:
{"message": "[Microsoft.Passive] 'being forwarded' looks like passive voice.", "location": {"path": "src/content/whats-new/2024/10/Whats-new-10-23-Kogs Gateway Logs Integration.md", "range": {"start": {"line": 64, "column": 56}}}, "severity": "INFO"}

## To get started:
By forwarding Kong Gateway logs to New Relic, organizations can effectively monitor and manage their API gateways, ensuring optimal performance and security.

Check warning on line 66 in src/content/whats-new/2024/10/Whats-new-10-23-Kogs Gateway Logs Integration.md

View workflow job for this annotation

GitHub Actions / vale-linter 

[vale] reported by reviewdog 🐶
[new-relic.ComplexWords] Consider using 'check' or 'watch' instead of 'monitor'.

Raw Output:
{"message": "[new-relic.ComplexWords] Consider using 'check' or 'watch' instead of 'monitor'.", "location": {"path": "src/content/whats-new/2024/10/Whats-new-10-23-Kogs Gateway Logs Integration.md", "range": {"start": {"line": 66, "column": 77}}}, "severity": "INFO"}

1. [Read our tutorial] (https://docs.newrelic.com/docs/tutorial-manage-large-log-volume/get-started-managing-large-logs/)
## To get started

1. [Read our tutorial](https://docs.newrelic.com/docs/tutorial-manage-large-log-volume/get-started-managing-large-logs/)
2. [Review our docs page](https://docs.newrelic.com/docs/logs/forward-logs/kong-gateway/)
3. [Explore our Logs UI overview](https://docs.newrelic.com/docs/logs/ui-data/use-logs-ui/)






0 comments on commit 96c1ecc

Please sign in to comment.