Download SolarWinds SAM

You can use SAM to monitor the health of Cisco UCS, Nutanix, Dell, HP, HPE ProLiant, and IBM hardware details such as temperature, fan speed, power supply, CPU, memory, and more. SAM provides instant visibility of hardware status (for example Up or Down); it can also calculate baseline data that can be used to configure hardware health thresholds. This section focuses on Dell, HP, HPE ProLiant, and IBM devices. See the SolarWinds Platform Administrator Guide to learn how to: Monitor Cisco UCS Devices. The first step is adding the parent UCS controller as an SolarWinds Platform node. Monitor hardware health for Nutanix clusters. After adding Hyper-V or VMware nodes for monitoring, add the parent Nutanix cluster and provide Controller VM (CVM) credentials.UCS and Nutanix hardware health monitoring does not currently support the SolarWinds Platform Remote Collector feature. To start monitoring hardware health for Dell, HP, HPE ProLiant, and IBM devices: Review the following topics:Monitor hardware health (SolarWinds Platform products Administrator Guide)Hardware health monitoring requirements for SAM Download, install, and configure agent software from third-party vendors so SAM can gather details that are not available natively from server operating systems. Click here for details. Run Discovery to detect third-party agent software on nodes, deploy agents that act as hardware health sensors, and automatically enable hardware health monitoring across multiple nodes. When Discovery enables hardware health monitoring for eligible devices, Asset Inventory data collection is also enabled for those nodes.Although Hardware Health and Asset Inventory can both be enabled automatically during Discovery, they can poll independently. For example, you can collect Asset Inventory data from a node once a day, and collect hardware health every 10 minutes. Note the following details about hardware health monitoring in SAM: In addition to using Discovery, you can enable monitoring in the Add Node Wizard or

This SAM application monitor template reports statistics gathered by SolarWinds NetFlow Traffic Analyzer (NTA). To learn about using NTA, see the NTA Administrator Guide.Note: This template was deprecated in fresh installations of SAM, starting in SAM 2020.2.1. We provide an updated version here, posted on June 30, 2021 that you can download and import into SAM. For details, see Import and export SAM templates in the SAM Administrator Guide.Changes in this updated template include:The Packet Dropped: Unmanaged Node component monitor is now called Packet Dropped: Unmanaged Flow Source.The Packet Dropped: Unmonitored Node component monitor is now called Packet Dropped: Disabled Flow Source.Two component monitors were removed: PDU Dropped: Unmanaged Interface and PDU Dropped: Unmonitored Interface.PrerequisitesWMI access to the target server.SolarWinds NTA is installed and licensed in your environment.CredentialsUser with administrative privileges on the target server.Component monitorsService: SolarWinds NetFlow ServiceThis component returns CPU and memory usage of the SolarWinds NetFlow Service. This service is responsible for receiving and saving data to the database as well as providing licensing information to the web console. If this service is stopped, data will not be collected.Cached Data Queue LengthThis monitor returns the amount of data not currently saved to the database. If this service is stopped or disabled, this data will be lost. This value should be as low as possible. If the returned value grows, the NTA server will not be able to save processed flows into the database. It is recommended that you adjust Top Talkers Optimization.Collapsed Records Per SecondThis monitor returns the amount of incoming records that are collapsed, per second.By default, this component monitor is disabled and should only be enabled for troubleshooting purposes.IP Address Cache SizeThis monitor returns the size of the IP address cache. This counter will function only when the DNS resolution is set to "persistent."By default,

Works through other methods until polling succeeds. You can also configure some component monitors to use SolarWinds Platform agents to collect data. WinRM is the default transport method used to collect data with the following WMI-based component monitor types: Directory Size Monitors File Count Monitors Performance Counter Monitors Process Monitors for Windows Windows Event Log Monitor Windows Service Monitors WMI Monitors See also: Configure WinRM polling in SAM 2024.4.1 and earlier Choose a fetching method for Performance Counter Monitors (SAM Template Reference) Component monitor thresholds For some component monitors, you can set threshold conditions on the monitored parameters to indicate warning and critical conditions. For example, to monitor the percentage of free space remaining on a volume, set a warning threshold at 15%, and a critical condition at 5%. See Manage application monitor thresholds in SAM. Component monitor scripts Some component monitors gather data directly from target services, others execute scripts on target servers to pull metrics. For example, the Apache template uses an SolarWinds Platform agent and several Linux/Unix Script Monitors to collect data. The IdleWorkers component monitor uses SSH to upload a script to target Linux servers and then processes the returned values and text output that appear in the SolarWinds Platform Web Console. The Active Directory 2016 Domain Controller Security template includes component monitors that use scripts to collect data: Locked out users uses a PowerShell script to pull metrics for currently locked out users. Disabled users uses a PowerShell script to return the number of currently disabled users; you can adjust thresholds as necessary. Other topics in this section include: View the Component Monitor Library in SAM Manage component monitors in SAM templates and application monitors Edit component monitors in templates and application monitors Use the Component Monitor Wizard in SAM Additional resources include: SAM Custom Application Monitor Template Guide (Learn how to use component monitors in PowerShell, Nagios, Linux/Unix, and Windows scripts.) SAM Template Reference (Learn about component monitors included in predefined templates.)Configure Linux/Unix systems for monitoring by the SolarWinds Platform agent in SAMConfigure Java Application Servers and JVMs for SAM monitoringChoose a fetching method

This SAM component monitor tests the ability of a TCP/IP-based service to accept incoming sessions. It tries to establish a socket connection using the Connect method of System.Net.Sockets. TcpClient class in the .NET framework. The elapsed time for a connection is saved as Response Time in the result. Statistic This component monitor does not compute a statistic. Prerequisites for SolarWinds Platform agent for Linux If using the SolarWinds Platform agent for Linux for monitoring, you only need to supply the port. No additional requirements are needed. Field descriptions Description A default description of the monitor. To override the default description, add to or replace existing text. Changes are automatically saved. The variable to access this field is ${UserDescription}.Customize descriptions to specify what will be monitored so related alerts and notifications are more meaningful later. Enable Component Determines whether the component is enabled. Disabling the component leaves it in the application in a deactivated state not influencing either SolarWinds SAM application availability or status. Port Number This field is the TCP protocol connection port. The default value is 80. Response Time Threshold Set the warning and critical threshold conditions based on the response time. The response time is the time in milliseconds it takes SolarWinds SAM to determine that a component is not Down and to retrieve any statistical data. See Application Monitor Thresholds. User Notes Add notes for easy reference. You can access this field by using the variable, ${UserNotes}.

With its built-in Microsoft SharePoint monitoring tools, SolarWinds Server & Application Monitor (SAM) can provide in-depth insight into performance. You can customize user-friendly dashboards to meet specific SharePoint monitoring needs, with key features like real-time metrics dashboards, alerting, and reporting, all in one place.SAM SharePoint monitoring tools include out-of-the-box components for you to monitor the following and more:Queued SharePoint requestsRequest wait timeCache APIWorker processTrack SharePoint service metrics related to search, text indexing, trace output, sending notifications, and performing scheduled tasks. With SAM, you can combine historical and real-time SharePoint performance metrics for a comprehensive SharePoint health check.Microsoft SharePoint monitoring tools in SAM make it easier to monitor server objects without individual logins to each server. It also allows for easy SharePoint monitoring of large farms from a single SharePoint monitoring dashboard, and it operates quickly due to its integration with Microsoft PowerShell. In addition, Server & Application Monitor offers native integration with SolarWinds Web Performance Monitor for synthetic transaction monitoring, showing you if a specific web transaction or a step is causing webpages and page elements to load slowly.With the right SharePoint monitoring software, you can get a deep understanding of your server's behavior. Using intuitive SharePoint monitoring tools like SolarWinds SAM can help you efficiently pinpoint SharePoint performance issues, so you can get a comprehensive overview of health with remediation solutions in no time.