Previous

Next

HPE Aruba EdgeConnect dashboard (light mode)

HPE Aruba EdgeConnect dashboard (dark mode)

Overview

This check monitors HPE Aruba EdgeConnect through the Datadog Agent.

HPE Aruba EdgeConnect is a Software-Defined Wide Area Network (SD-WAN) platform used to connect branch offices, data centers, and cloud environments through an overlay of secure tunnels managed centrally by an Orchestrator. This integration authenticates against the Orchestrator and individual EdgeConnect appliances to collect health and performance metrics from each appliance's REST API and minute-stats archives. It also reports the SD-WAN fabric topology (devices, interfaces, and tunnels) to Network Device Monitoring (NDM).

What this integration monitors

The integration collects metrics across multiple layers of the EdgeConnect SD-WAN fabric, including:

• Orchestrator and appliance inventory: Discovers all EdgeConnect appliances managed by the Orchestrator. Surfaces reachability status, uptime, hostname, site, model, and software version.
• Appliance health: Reports CPU, memory, and disk usage percentages, as well as hardware alarm state, to detect overloaded or failing devices.
• Network interfaces: Provides administrative and operational status, configured speed, RX/TX bandwidth and rate, peak and average utilization, and forward-drop counters per interface.
• SD-WAN tunnels: Reports per-tunnel latency, jitter, packet loss (pre- and post-Forward Error Correction (FEC)), Mean Opinion Score (MOS) for voice-quality tracking, downtime during the interval, and bidirectional throughput in both bits and packets per second. Detects path degradation and Service Level Agreement (SLA) violations across the overlay.
• Internet breakout tunnels: Monitors RX/TX bandwidth, peak rates, and configured maximum throughput on local-internet breakout tunnels to observe direct-to-cloud traffic.
• Quality of Service (QoS) and traffic shaping: Tracks per-Differentiated Services Code Point (DSCP) class bandwidth and rate counters, shaper drop counts, and drop percentages. Useful for validating QoS policies and spotting classes being starved or oversubscribed.
• Circuit SLA probes: Reports average latency, jitter, and packet loss from SLA probes, plus next-hop administrative and operational status, to monitor underlay link quality independently of the overlay.
• Application performance: Provides per-application latency, enabling you to trace tunnel or interface issues to the specific affected applications.
• Network Device Monitoring topology: Pushes device, interface, and tunnel metadata to NDM, enabling visualization of the SD-WAN fabric and correlation with the rest of the network.

Setup

Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the Autodiscovery Integration Templates for guidance on applying these instructions.

Installation

The HPE Aruba EdgeConnect check is included in the Datadog Agent package. No additional installation is needed on your server.

Configuration

1. Edit the hpe_aruba_edgeconnect.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your HPE Aruba EdgeConnect performance data. See the sample hpe_aruba_edgeconnect.d/conf.yaml for all available configuration options.

   Note: Monitor permissions are enough to collect most metrics. Admin permissions are required to collect the hpe_aruba_edgeconnect.device.cpu.usage metric on the appliances. If the configured credentials do not have admin access, the Agent skips this metric, but collects the rest of the metrics.

2. Restart the Agent.

Validation

Run the Agent’s status subcommand and look for hpe_aruba_edgeconnect under the Checks section.

Data Collected

Metrics

Logs

The recommended way to collect logs from HPE Aruba EdgeConnect is to configure the appliance to forward logs through syslog. For more information, see the HPE Aruba Networking documentation.

1. Enable log collection in your datadog.yaml file:

   logs_enabled: true
   

2. Uncomment and edit the logs configuration block in your hpe_aruba_edgeconnect.d/conf.yaml file. For example:

   logs:
     - type: tcp
       port: 10514
       source: hpe_aruba_edgeconnect
       service: <SERVICE>
   

Events

The HPE Aruba EdgeConnect integration includes alarm event support. Events are disabled by default; to enable them, set collect_events to true in the configuration.

Service Checks

The HPE Aruba EdgeConnect integration does not include any service checks.

Uninstallation

To disable the integration, rename the configuration file from hpe_aruba_edgeconnect.yaml to hpe_aruba_edgeconnect.yaml.example. Alternatively, if you are running a containerized environment, you can remove the annotation used to enable the integration.

Support

Need help? Contact Datadog Support.