NCP
  • Network Copilot
  • What's New?
  • Quick Start
  • Getting Started
    • System Requirements
      • On-Prem Deployment
      • Cloud Deployment
    • Licensing
    • Metrics Matrix
    • Onboarding Data
    • Scalability
  • Downloading Network Copilot
  • Deploying & Managing Network Copilot
    • Deployment Prerequisites
    • Installing Prerequisite Packages
    • Deploying the NCP Package
    • Managing Network Copilot
      • Upgrading License
      • Upgrading NCP
      • Uninstalling NCP
  • Web UI Administration
    • License Activation
    • Login Page
    • Dashboard Overview
    • Inventory Management
      • Onboarding Switches
        • Using ONES Telemetry Agent
        • Using SNMP
          • Adding Switches using YAML
          • Adding Switches using CSV
        • Using sFlow
        • Using API
        • Using gNMI
    • User Accounts
  • Accessing NCP
  • External Integrations
    • Communication & Collaboration
      • NetBox
      • Cisco Nexus Dashboard
      • Slack
    • Data Ingestion
      • AWS S3
      • Azure
      • ELK Stack
      • Google Cloud Storage
      • InfluxDB
      • Loki
      • Snowflake
      • Splunk
  • Use Cases
    • Basic NetOps
    • Flow Analytics
    • Security Audits
    • Inventory Insights
    • Support Knowledge Base
    • Upgrade Compliance
  • Contact Aviz Networks Support
Powered by GitBook
On this page
  • Overview
  • Configure ELK as a Data Source in NCP

Was this helpful?

Export as PDF
  1. External Integrations
  2. Data Ingestion

ELK Stack

PreviousAzureNextGoogle Cloud Storage

Last updated 22 days ago

Was this helpful?

Overview

This section guides you through configuring and running the integration between the ELK Stack and NCP

By following these steps, you'll enable NCP to:

  • Pull and index logs from Elasticsearch for real-time visibility.

  • Allow users to query logs and telemetry data using NCP’s chat interface.

  • Improve troubleshooting efficiency and accelerate root cause analysis.

Prerequisites

Before you begin, ensure the following:

  • Elasticsearch Endpoint: URL of your Elasticsearch instance (e.g., https://elk.example.com:9200)

  • Index Information: The names of the indices that contain relevant network logs (e.g., network-logs-*, telemetry-*)

Configure ELK as a Data Source in NCP

To integrate your ELK Stack with NCP:

  1. Log in to the NCP GUI

  2. Navigate to Settings → Data Sources → ELK

  3. Click Add Configuration

  4. Enter the following details:

    • Name: A friendly name for your ELK data source

    • Elasticsearch URI: Base URL of your Elasticsearch instance (e.g., https://elk.example.com:9200)

    • Index Patterns: Specify the indices or wildcard patterns to fetch logs from

  5. Click Save to complete the configuration