According to the SolarWinds NPM Administrator Guide, you can assign different permissions to user accounts to control their access and actions in the Orion Platform. One of the permissions is “Allow Account to Clear Events and Acknowledge Alerts and Syslogs”, which enables the user to acknowledge alerts, clear events, and mark syslogs as read. This permission is required for a user to be able to acknowledge alerts, as acknowledging an alert stops the escalation process and provides an audit trail. The other permissions listed are not related to alert acknowledgment. “Allow Account to Unmanage Objects” allows the user to temporarily stop monitoring selected network objects. “Allow Node Management Rights” allows the user to add, edit, and delete nodes and interfaces. “Allow Administrator Rights” grants the user full access to all Orion Platform features and settings.  References :  SolarWinds NPM Administrator Guide , page 69-70;  Add or remove an alert acknowledgment .

Capacity usage trends are calculated based on historical data. By default, the longest time period taken into account for calculating the capacity forecast is 180 days. The more historical data up to 180 days are available, the more precise is the calculated forecast. Forecast calculation methods include peak calculation and average calculation, which can be set globally or customized for individual objects. Capacity forecasting is available for nodes, interfaces, and volumes that meet certain requirements, such as being managed in NPM and having enough historical data in the database.  References :  Monitor capacity usage trends on the network and forecast capacity issues in NPM ,  Forecast capacity for nodes, interfaces, or volumes in NPM ,  Real-Time Network Monitoring Tool

The best way to reduce false alerts for high traffic utilization is to configure the alert trigger condition to be more specific and accurate. By setting the alert to trigger only when traffic utilization remains high for a sustained period, you can avoid getting alerted for short-lived spikes that are not a cause for concern. You can use the  Time of Day  and  Trigger Condition  options in the alert configuration wizard to define the duration and threshold of the high traffic utilization condition. For example, you can set the alert to trigger only when traffic utilization is greater than 80% for more than 10 minutes during business hours.  References :

How do I create a high transmit percent utilization alert to monitor interface bandwidth - Forum - Network Performance Monitor (NPM) - THWACK Products

How alerts work - SolarWinds

SCP Study Aid - SolarWinds  (page 8)

NPM uses SNMP to collect utilization statistics from network devices, such as routers, switches, firewalls, etc.  If NPM only shows Availability and Response Time statuses for a device, it means that SNMP is not configured correctly on that device or NPM cannot access the device via SNMP 1 . Some possible reasons for this are:

The device does not support SNMP or SNMP is disabled on the device

The device has a different SNMP version or community string than NPM

The device has a firewall or access control list that blocks SNMP traffic from NPM

The device has a misconfigured SNMP agent or MIB To troubleshoot this issue, you can use the SNMP Test Tool in NPM to verify the SNMP settings and connectivity of the device 2 .  You can also check the device logs and configuration to ensure that SNMP is enabled and properly configured 3 .  References :  1 : Network Performance Monitor Administrator Guide - Troubleshoot SNMP issues  2 : Network Performance Monitor Administrator Guide - Test SNMP access  3 : Network Performance Monitor Getting Started Guide - Troubleshoot SNMP issues

https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-configuring-trap-viewer-filters-and-alerts-sw272.htm https://documentation.solarwinds.com/en/success_center/orionplatform/content/lm/la-orion-log-viewer.htm

By default, NPM uses the global critical CPU threshold for node statuses, which is 90%. However, you can override this threshold for individual nodes by editing their properties and specifying a custom value for the critical CPU threshold. This way, you can adjust the threshold according to the specific characteristics and performance of each node. Changing the critical CPU threshold on the node will affect how the node status is calculated and displayed in the web console, as well as how the alerts are triggered based on the CPU utilization.  References :  Thresholds in the SolarWinds Platform ;  CPU Critical Threshold - Forum - Network Performance Monitor (NPM) - THWACK

https://support.solarwinds.com/SuccessCenter/s/article/VMAN-and-IVIM-feature-comparison?language=en_US

To show the connection between two devices on an Orion map, you need to meet the following requirements 1 :

The devices must be monitored by NPM.

The devices must support topology and be interconnected.

The devices must have the corresponding interfaces monitored and identified as full or half duplex.

The Orion Maps feature must be enabled and configured.

If you do not see the connection between two devices on an Orion map, you should first verify that you are monitoring Layer 2 and 3 topologies for the devices. You can do this by checking the NPM Network Topology widget on the device details page.  This widget will reflect what connections will be automatically drawn in Orion Maps 2 .  If the widget does not show the expected connection, you may need to enable topology polling for the devices or check the SNMP credentials and configuration 3 .

If you are monitoring the correct topologies and still do not see the connection, you can build a custom connection between the devices using the Orion Maps feature. In the Map Editor, you can add the two devices to the canvas, select them, and click the Connect Objects button.  Here you can specify the interface on either side and choose to add the manual connection to the database 2 .

Building a new Orion map and adding the related entities instead of the nodes will not resolve the issue, as the related entities are based on the same topology data as the nodes.  Changing the monitoring method from SNMP to CLI will not resolve the issue, as CLI is not supported for topology polling 3 .

When a router monitored by NPM reboots, the interface indexes may change, causing the interface statuses to become unknown in NPM. This is because NPM uses the interface indexes to identify and poll the interfaces. To resolve this issue, you need to remove the unknown interfaces from NPM and then run a list of resources on that node to discover the interfaces with the new index IDs. You can then add the interfaces back to NPM and resume monitoring them.  References :

Allow Change the Interface Index - Forum - Network Performance Monitor (NPM) - THWACK Products

Edit interface properties in NPM - SolarWinds

SCP Study Aid - SolarWinds  (page 6)