The document provides an overview and agenda for a training session on SolarWinds Profiler Storage, Virtual, and Server products. It covers Profiler architecture, file analysis features, configuring alerts, troubleshooting agent reporting issues, and optimizing performance through load balancing. The session demonstrates how to use file analysis, configure alerts, troubleshoot agents, and ensure proper workload distribution across agents and servers. Attendees learn how to effectively monitor, manage and troubleshoot their storage, virtual, and server environments using Profiler.
2. SolarWinds Subject Matter Experts Dan Wendeln- Education and Certification Manager Brian Radovich – Product Manager, Storage Today’s Topic: Customer Training – Profiler Storage, Virtual and Server Introduction
3.
4. If not, use the GoToWebinar chat or Q&A panel to let us know.
9. Goals for today’s training session By the end of this session you should understand: Profiler Architecture & System Recommendations File Analysis Features Alert Configuration and Best Practices Troubleshooting Agent Reporting Issues Load Balancing and Resource Management in Profiler
10. Profiler and the SolarWinds Portfolio SolarWinds manages Network Devices Routers, Switches, Firewalls Servers Physical and Virtual Software Applications Exchange, SQL Storage Devices SAN array, NAS, DAS SolarWinds products Periodically check device performance Alert network administrators of problems Report on overall performance Identify and diagnose issues Resolve network issues Network Storage Apps
53. By file extension (.dmp, .tmp, .core, etc.)File Analysis – Using Rules A file rule defines files that you would like to find. To create a file rule: Create the rule. Assign it to a policy. Push the policy out. All file analysis runs will also output the files that meet the criteria of the rule.
82. Agent Troubleshooting Almost all agents are yellow on the Server Monitor. Some data is not being collected If all the agents are yellow & the times are greater than 2 or 3 minutes, check the event receiver If all the agents are yellow & the times are less than 2 or 3 minutes, check the collector One or more agents are yellow on the Server Monitor. Press the stoplight to validate communicate & review which modules are online and offline If not receiving real time, review the logs to see if some data is not available If you can’t communicate with the agent, go to that agent & review the core.xml and kernel.log. If you see fatal.log, it is usually a configuration issue
83. More Troubleshooting Tips Event Receiver Issues: Check to see if the service is running. Another application could be using port 162 (port is configurable). Collector Issues: In large environment you can run the collector out of memory. This implies you should spread the load to more poller agents. If the collector loses the connection to the database, it may stop collecting. If the database is up, restart the collector. If the database is down, start the database & then start the collector.