Network Discovery is an automated process to scan subnets and import new infrastructure. However, the discovery engine includes logic to prevent duplicate entries and ignore non-relevant assets. According to the SolarWinds Platform Administrator Guide, if specific devices are missing from the results, the most common administrative cause is theDiscovery Ignore List.
The "Ignore List" is a database of IP addresses or MAC addresses that the platform has been explicitly told to skip. This often happens if a device was previously discovered but the administrator chose "Ignore this node" during the import phase. The system remembers this choice to prevent the device from reappearing in every subsequent scan. Additionally, the platform automatically ignores any node that isalready presentin the
"Manage Nodes" list to avoid creating redundant monitoring objects.
While a timeout (Option C) or incorrect polling method (Option D) could cause a node to fail to respond with its full metadata, the device would typically still appear in the discovery results as a "Generic" or "ICMP- only" device rather than being skipped entirely. Only theIgnore Listor pre-existing status causes a device to be excluded from the discovery results table during a scan of a valid subnet.

AppStackis designed to provide a "top-to-bottom" visual representation of the IT infrastructure layers that support an application. According to theSolarWinds Platform Administrator Guide, the AppStack Environment view automatically maps relationships between specific monitored entities.
The two primary categories that appear in this view aredatabase instances (A)andservers (C). In a typical application stack, the "Server" represents the physical or virtual hardware, while the "Database Instance" (monitored via AppInsight for SQL, Oracle, etc.) represents the software layer running on that server.
AppStack visually links these so that if a database instance shows a critical status, an administrator can instantly see which server it is hosted on and if there are underlying infrastructure issues. Other common categories include Applications, Transactions, Virtual Hosts, Clusters, and Volumes.
NetFlow(Option B) is a traffic analysis technology used in the NetFlow Traffic Analyzer (NTA) and is generally not a primary "entity" category in the standard AppStack environment map.SNMP Pollers(Option D) are the backend mechanisms used to collect data; they are a configuration component rather than a logical infrastructure entity that would be represented as a layer in an application dependency stack.

Custom Views(Summary Views and Detail Views) are the primary way administrators control the layout and focus of the SolarWinds Web Console. According to theSolarWinds Platform Administrator Guide, views are used to tailor the platform to different user roles.
The two primary reasons for creating them are:
* Limit user access to specific elements (A): Views can be restricted to specific users or groups. By creating a custom view that only contains "Storage" widgets and assigning it to the Storage Team, an administrator can effectively limit what those users see when they log in. This prevents users from being overwhelmed by irrelevant data and acts as a functional layer of access control.
* Personalize user experience and focus on specific elements (D): Different roles require different data. A CXO might need a high-level "Map" and "SLA Trend" view, while a technician needs a "Top
10 Nodes by CPU" and "Active Alerts" view. Custom views allow the administrator to curate exactly which widgets are visible, ensuring that each user has the most relevant information for their job front- and-center.
SQL customizations(Option C) are a method of building widgets, but not thereasonfor the view itself.
Monitoring new elements (Option B) is handled through theAdd NodeandPollerssettings; a view onlydisplays what is already being monitored.

When new users are added to the SolarWinds Platform, they are typically granted a "Standard User" baseline of permissions to ensure they have immediate visibility without administrative risk. According to the SolarWinds Platform User Account Managementguides, the two primary default rights arelog into web console (B)andview existing reports (D).
The ability to log into the web console is the fundamental prerequisite for any user interaction with the platform. Once logged in, the "View Existing Reports" permission allows the user to navigate the report manager, search for historical data, and run or export reports that have been shared with them. These permissions are considered "safe" or "read-only" baseline rights. In contrast,Edit Views (A)andManage Reports (C)are administrative-level permissions that are disabled by default. "Edit Views" allows a user to change the dashboard layout for everyone, and "Manage Reports" allows for the creation, deletion, and scheduling of reports. By restricting these to an "opt-in" basis, SolarWinds protects the integrity of the monitoring configuration while ensuring that every team member can access the information they need to perform their daily duties.

Anomaly-Based Alertingrepresents a shift from static thresholds to behavioral analysis in the HCO platform.
According to theSolarWinds HCO Alerting Enginedocumentation, this feature uses machine learning to establish a "baseline" for specific metrics like CPU load or memory usage over a period of 7 to 30 days.
The primary benefit is that itanalyzes entity behaviorand triggers an alert only when a metric deviates significantly from its historical "normal" for that specific day and time. For example, if a server traditionally runs at 90% CPU during a Sunday night backup, a static 80% threshold alert would trigger a "false positive" every week. Anomaly-based alerting learns this behavior and will only fire an alert if the CPU hits 90% on a Tuesday morning when the normal load is only 20%.
This reduces alert noise by focusing ontrue anomaliesrather than simple threshold violations. It does not
"remove the requirement for trigger conditions" (Options B and C); instead, it replaces a static numerical threshold with a dynamic, machine-learned threshold. The administrator still defineswhichentities to monitor andhowsensitive the anomaly detection should be.