Comprehensive and Detailed Explanation From Exact Extract:

Applications and NBAR2 applications in top applications are sorted by bytes: The default sorting for the “Top Applications” view, including NBAR2 apps, is by bytes.

It is possible to combine applications and NBAR2 applications: SolarWinds allows combining standard and NBAR2-classified apps for alerting and reporting purposes.

Exact Extract from Official Guide:

"Top Applications, including NBAR2, are sorted by bytes and you can combine standard and NBAR2 application data in alerts and reports."

— (Network Performance Monitor Administrator Guide, “NBAR2 Applications” section)

Comprehensive and Detailed Explanation From Exact Extract:

If an OID is not present in the SolarWinds MIB database, you can still poll it by manually defining the OID in Device Studio. The platform allows you to input the object identifier and specify SNMP as the method to query the device.

From the documentation:

"If a required OID is missing from the MIB database, use the Device Studio's 'Manually Define Object Identifier' feature to specify the OID and configure SNMP polling for the device."

Comprehensive and Detailed Explanation From Exact Extract:

Custom pollers are typically created when you need to monitor metrics or OIDs that are not supported by default in SolarWinds:

Monitor specific metric that is not out-of-the-box: If a device exposes a metric not natively monitored by SolarWinds, you must create a custom poller for that metric.

Monitor unsupported object ID: For any OID that is not included in default templates, a custom poller is necessary.

Monitoring special equipment or devices without WMI might also need custom pollers, but the requirement specifically applies when you need to access non-standard metrics or OIDs.

Comprehensive and Detailed Explanation From Exact Extract:

If a device studio poller is configured with a static textual value (rather than a dynamic OID), any change in the actual value on the node will not be detected automatically; the poller’s configuration must be manually updated to reflect the new value. OID-based pollers update automatically as values change on the device.

Comprehensive and Detailed Explanation From Exact Extract:

Device Studio is designed to enable support for complex devices and can poll multiple OIDs as part of a single custom poller definition. While Universal Device Poller (UDP) is also used for custom SNMP polling, it is generally limited to a single OID per poller. Device Studio is intended for use cases that require combining and correlating multiple OIDs for richer, template-based device monitoring.

Comprehensive and Detailed Explanation From Exact Extract:

SolarWinds allows you to confirm which metrics (contributors) are used to determine node status. In the node status contributors configuration, you can check if CPU load is included for status calculation. This ensures that CPU thresholds are considered when evaluating overall node health.

Comprehensive and Detailed Explanation From Exact Extract:

SolarWinds Hybrid Cloud Observability (HCO) supports capturing flow data and CBQoS data using:

A. IPFIX: (IP Flow Information Export) is the IETF standard for exporting flow information, supported for both flow data and CBQoS.

C. NetFlow: Developed by Cisco, widely used for flow and CBQoS data collection.

J-Flow is primarily for flow data (from Juniper devices), and SNMP is not a flow export protocol.

The documentation states:

"NetFlow (including NetFlow v9) and IPFIX are supported for flow and CBQoS data collection. These standards provide extensive network traffic and QoS visibility within HCO."