• /
  • EnglishEspañol日本語한국어Português
  • ログイン今すぐ開始

Forward logs from Kong Gateway to New Relic

October 26, 2024

Gain valuable insights into API gateway performance, health, security, and usage

  • Learn more
  • Get started

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.

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

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 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 . See an example of the manifest configuration file in the Configure the File Log plugin section.

Step 3: Apply the Log File Log plugin configuration

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

    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 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.

To get started

  1. Read our tutorial
  2. Review our docs page
  3. Explore our Logs UI overview
Copyright © 2024 New Relic株式会社。

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.