stevenstadel · Monitoring Addict · ✭✭✭✭✭

Yes, my solution is to restrict the CIDRs that I am not interested in. Click edit and add a filter like Subnet.CIDR not in (26,27,28,29,30,31,32)

Try running all 300 through the network discover wizard, then try the method outlined again.

Settings - All Settings - Manage Pollers - Search for hardware Health Sensor and click assign, sort by vendor, and apply to the Cisco Devices. 

Default retention of Logs, Syslogs, and Traps is 7 days. You will need to look at Log Analyzer to determine what is sending you those excessive logs and either have that stopped or create rules to remove them Check out this KB -solarwindscore.my.site.com/.../Truncate-the-SolarWindsOrionLog-tables

You can add a SWQL query to a report that may get you closer. SELECT n.Caption AS [Server Name], -- n.Vendor, v.Caption AS [Volume], ROUND(v.VolumePercentUsed, 0) AS [Percent Used], ROUND(v.Size / 1073741824.0, 1) AS [Size (GB)], ROUND(v.VolumeSpaceUsed / 1073741824.0, 1) AS [Used (GB)], ROUND((v.Size - v.VolumeSpaceUsed)…

Netflow is configured on the switch itself to send the flows. Verify that the flows are enabled and are being sent to the SolarWinds pollers. https://documentation.solarwinds.com/en/success_center/nta/content/nta-cisco-netflow-configuration-sw1982.htm

Where is the disk space being used? Grab a program like treesize or windirstat and see where the consumption is your logs may not be the issue.

One way would be to create groups for each site, then add a dynamic rule using using custom properties to populate those groups. Add Lat and Long to the groups and they will show up on your worldwide map…

Sure, you will need to add in the missing properties that you want to see in the SWQL statement. I am not sure of your custom property name but this may get you close to want you want. SELECT DISTINCT c.Name, n.Caption, n.IPAddress, n.CustomProperties.node_category, FROM Orion.ContainerMembers cm LEFT JOIN Orion.Nodes n ON…

Virtual infrastructure with fast SSDs. The flexibility you get with virtualization (snapshots, host migration, host redundancy, ability to add/remove CPU and Memory etc.) are superior to physical hosts. SQL enterprise with core based licensing in a 3 node Always On configuration over 2 DCs.

The approach will be to use accounts to limit the devices each department can view. For example: Dept A, Dept B, and Managers. First create SolarWinds groups that contain the devices you want the individual depts to see. Documentation Create Groups. Settings - All Settings - Manage Groups - Add New Group. Name your group,…

Scheduled Maintenance is a feature of 2025.2 RC. Release Notes If you want a workaround until you get that in place you can use the Manage Nodes view to sort by polling engine and then schedule the muting of the nodes.

This depends on how your users access the platform. If they are using a load balancer that has a bunch of servers in a pool you would be fine, if they are using a direct URL to the webserver that you are moving then you would be taking an outage during your migration.

This is a good use case for using groups for view limitations. Setup different groups that use dynamic queries that use your custom properties for each use case, then apply the groups to the accounts that you would like restricted access 

In High Availability settings there is a default setting that will let the default email acct know if there is a HA server status change. 

You will hit limits with SQLExpress quickly.

IOPS are provided out of the box if you use the agent. I highly suggest it for Linux servers.

SWQL does not support referencing an alias in the same SELECT block if that alias is defined by a subquery, expression, or function. In your original version, scalar subqueries are used in the SELECT clause and aliased as RunningBackupTime, StartupBackupTime, etc. These aliases cannot be reused in CASE statements or ORDER…

I do not know of a document for the administrative / operational status icon types. I just hover over the icon and read the output. Will you use the topology information? If there is no use case then there is no need to collect it. This isn't really a monitor but a data collection. Depending on your router / switch there…

This all goes to what you want observed. Monitor the things that are important to your environment / or things you want a easily reportable inventory on. There are a huge amount of metrics available when polling devices. Ask yourself if in your environment that you need or want these metrics and how you would use the info.…

What if you try removing the two comments in the query? "-- Put whatever filters here -- Start on the first day of the previous month (inclusive)" and "-- End on the first day of this month (non-inclusive)"

Always the best method!

All you really need to do is repoint to the new IP that points to your DB. Shut everything down, then run the config wizard.…

Start with setting up a Windows event log monitor, then setup an email alert to trigger when that is set. Alert Documentation

You need to setup a New Universal Device Poller to retrieve the OID using the UnDP program on the polling engine. metric. https://documentation.solarwinds.com/en/success_center/npm/content/core-monitoring-mibs-with-universal-device-pollers-sw548.htm This is different from changing the sysobjectid. in the GUI. You then test…

SAM is Server and Application Monitor. When creating an alert you would reference the SAM application monitor that was created and put the thresholds directly in that template. If you are alerting off of your UnDP poller you would set the alert to be Custom Node Poller. Are you seeing values being polled for the Dataplane…

Try this App Template to pull the different CPU (Dataplane vs Management) - Palo Alto Metrics - Application Monitor Templates - Server & Application Monitor - THWACK (solarwinds.com) I personally prefer using SAM, if possible, for polling SNMP because I can get more advanced features like using Baseline Metrics. If you…

Try C:\ProgramData\SolarWinds\Logs\Orion\ActionsExecutionAlert.log. If if isn't showing enough detail change the level of detail for Actions Execution.

Location was originally used to store the data from SNMP Location values, when the windows agent was introduced the field was repurposed for those specific machine types. The location value when it was solely collecting from SNMP was only valuable if you had a rock solid build process and people following the same naming…

To get you working quickly change the config on the switch to a supported algorithm for the version you are running. As shown in the article https://solarwindscore.my.site.com/SuccessCenter/s/article/Supported-algorithms-and-cipher-for-NPM-and-NCM?language=en_US new versions of the platform support updated algorithms. The…