Documentation forNetFlow Traffic Analyzer
Analyzing network traffic and bandwidth is a key capability of Hybrid Cloud Observability Advanced and is also available in a standalone module, NetFlow Traffic Analyzer (NTA). Hybrid Cloud Observability Advanced and NTA are built on the self-hosted SolarWinds Platform.

Monitor CBQoS dynamically in NTA

This section assumes that you set up your CBQoS policies and applied them to interfaces on your devices, and that devices are all being monitored in NPM and are listed in NTA as CBQoS Sources.

For more information on discovering network devices, see Discovering and Adding Network Devices.

For more information on setting up on NetFlow collections, see Set up network devices to export NetFlow data.

Should data matched for CBQoS processing violate your expectations as expressed in the form of alert threshold settings, you can have NTA trigger an alert and take specific actions.

The following SolarWinds Platform Advanced Alerts are available to you:

  • Pre-Policy
  • Post-Policy
  • Drops

For more information about individual alerts, see CBQoS Alerts.

Configure a CBQoS alert

  1. Click Alerts & Activity > Alerts.
  2. Use the Group By list to filter alerts.
  3. Select the relevant CBQoS alert.
  4. Click Edit Alert Definition.

    1. On Properties, click Enabled to turn the alert on, and then select an Evaluation Frequency of Alert.

    2. On Trigger Condition, define the conditions in which the software launches the alert.

      For the CBQoS alerts, the default condition is a match on the SQL query. You can adjust the number of seconds for which the match exists, essentially inserting a delay to allow the traffic to fluctuate without triggering the alert. You can adjust this condition or add conditions.

    3. On Reset Condition, define the conditions in which the software resets the alert.

      For the CBQoS alerts, the default condition is no match on the SQL query. You can adjust the number of seconds for which the match fails to persist, essentially inserting a delay to allow the traffic to fluctuate without canceling the alert.

    4. On Time of Day, define the days and times during which the software actively evaluates the database for trigger conditions.

      The default is Always Enabled.

    5. On Trigger Actions, create actions to execute when the software triggers the alert.

      As discussed, the default action for all alerts is to write to the SolarWinds event log.

      For CBQoS alerts, the default actions include write the same event message into an email and send it to a contact.

    6. On Reset Actions, define actions to execute when the software resets the alert.
  5. Click Next, and click Submit.