Services

Explore Kyndryl Bridge Services

WAN Networking Dashboard
Published On Jun 02, 2026 - 4:18 AM

WAN Networking Dashboard

Learn how to configure this dashboard and the information it provides.
WAN networking now offers a centralized dashboard that provides crucial insights into network health and stability, underscoring its importance to network engineers and system administrators. The dashboard data is generated using a producer-consumer model, with the AIOPS Data Streaming service acting as the communication layer.

Technical prerequisites

To ensure that WAN dashboards function properly, it is crucial to first deploy the Network Metrics Consumer. This consumer is typically deployed in each compute zone and must be configured to use the topic delivery-network-wan-metrics-source.
Additionally, a producer must be deployed to supply data to the consumer extension. This dashboard is vendor-agnostic, meaning it can work with different vendors. Currently, either the Cisco SD-WAN Producer or the Fortinet SD-WAN must be deployed to provide data to the consumer.
Here are the steps to configure the WAN Networking Dashboards:

Network Metrics Consumer Extension

  • Application Name:
     Name you give the extension.
  • Description:
    Explain how this extension will be used and note any specific details relevant to this instance.
  • Replicas:
     The number of consumer copies to be created is typically three during the development phase.
  • Synapps Topic:
     The subject used to access your messages on the data streaming service (DSS).
  • Consumer Group:
     You can specify the name of the data streaming service (Kafka) queue from which you want to retrieve messages. This can be set to any value you prefer. If you need to access messages from the beginning of time, or as far back as the Data Streaming Service (DSS) retains them, consider using a new queue.
  • Elastic TLS:
     This setting is disabled because the internal Elastic connection typically does not use TLS.
  • Use Proxy:
     It is typically set to false because the Elasticsearch connection is usually internal.
  • Bulk metrics field:
     The field in this topic holds the list of expected metrics.
  • Index Field Name:
     Field on the topic indicates which index the data should be inserted into, which is almost always suitable as the default.
  • Log Level:
    Logging levels can be set to DEBUG, INFO, WARNING, or ERROR, with DEBUG being the most verbose and ERROR the least.
  • Set the polling interval:
    To meet your network's requirements and provide control over data freshness and system responsiveness.

Deploy the Cisco SD-WAN Producer

  • Application Name:
    Name you give the extension.
  • Description
    : Explain how the extension will be utilized and note any significant details for this specific instance of the extension.
  • Cisco vManage URL:
     The url to Cisco vManage.
  • Enable TLS:
     It's usually set to false since the internal DSS connection typically doesn't use TLS.
  • Cisco vManage Username:
     Provide the Cisco vManage username for API access.
  • Cisco vManage Password:
    Username for Cisco vManage.
  • Log Level:
    Set the logging level to DEBUG, INFO, or WARNING to adjust the verbosity of logging in the extension, from most to least detailed.
  • Polling interval:
    How often to poll vManage for new stats. Defaults to 5 mins.
  • Enable Proxy:
    This field typically defaults to false in production, indicating whether the AIOPS proxy should be used.

Deploy the Fortinet SD-WAN

  • Application Name:
    Name you give the extension.
  • Description:
    Explain how this extension will be utilized and note any important details for this particular instance.
  • Polling interval:
     The polling interval for vManage to retrieve new statistics is set to 5 minutes by default.
  • Log Level:
    Logging levels can be set to DEBUG, INFO, or WARNING, generating output from most to least verbose in the extension.
  • Enable Proxy:
     This field, typically set to false in production, indicates whether to use the AIOPS proxy.
  • Fortinet FortiManager URL:
    The url to FortiManager
  • Fortimanager API key:
    Requesting an API key for FortiManager, as the user requires access to the API.
  • Enable TLS:
    Typically, this is set to false because the internal DSS connection usually does not utilize TLS.

KPIs Metrics

The table below describes and calculates each KPI/metric used in the insight.

WAN Networking Home

Summary of the inventory for all WAN devices from Cisco vManage and Fortinet FortiManager. The dashboard displays metrics such as IP address, device name, model, and type.

WAN Networking System

KPIs for measuring device health from Cisco vManage and Fortinet FortiManager include monitoring uptime to determine the last reboot time. The metrics displayed on this dashboard are system CPU, memory, reachability, disk usage, and uptime.

WAN Networking Interfaces

Key Performance Indicators (KPIs) for measuring interface and device traffic from Cisco vManage and Fortinet FortiManager include interface throughput (kilobits per second, kbps) for both incoming and outgoing traffic, errors (incoming, outgoing, and total), and total packets. These metrics are presented in this dashboard.
Do you have two minutes for a quick survey?
Take Survey