taylor.crowley · SolarWinds Engineer · ✭✭✭✭✭

As far as I'm aware, with SCM, you either monitor a component or you don't. There is no way to ignore specific components on a server so that they aren't alerted on at the Server HW Inventory level, similar to how you can turn off the status change for interfaces, volumes, nodes etc. However, you may be able to add an…

The colours used elsewhere in the platform are fine, in my opinion, it's just the Orion Maps which has the washed-out green, which in most cases is fine, but certain NOC views may suffer. It would be interesting to see that extra layer of customisation, but I think it's especially important for maps. Take this view on a…

Can't pick a favourite, but my top 5 are The Witcher 3, Deus Ex: Human Revolution, Baldurs Gate 3, The Outer Wilds, and basically all of the mainline Resident Evil Games....

Currently an apprentice, training to become a SolarWinds Professional/Network Technician

What marvellous news to wake up to! It's an honour 

I think there should be an option to set colours as defaults for all maps yes

@"bmrad" any further on this?

Yeah so I'm not saying to allow us to assign Purple as an UP status it would just be nice if it was more consistent throughout so that green POPS where we arent using the status for icon option in Orion Maps which btw shows the perfect kind of green that I would want to set for the border

We have a customer with many VRFs who would find this feature extremely useful. Are there any updates on this feature being implemented?

Yes please go ahead and do that

@"kpina" Should Jan 19th question include a "Select ALL that apply"? Didn't realise it was multiple choice

@"bmrad" That's great! My only other want would be to know how SolarWinds is gathering that NEXT RUN data. As mentioned, it is stored in the DB in a CRON expression in the Orion.Frequencies table. If a user wanted to display this on a Modern Dashboard, for example, how would the SWQL be written to interpret that CRON?

Thank you good sir

If I use my above screenshot as an example the issue is as @tvminser describes where the default green is just too light for some circumstances. We would like the ability to choose a custom colour to display based on the Status so that it might look more like this when a Node is UP: As it stands I have to set that colour…

SELECT COUNT(InterfaceID) AS DownInterfaces FROM Orion.NPM.Interfaces WHERE Status = 2 So above we are using the COUNT function, which will just count however many rows are brought back by whatever item you specify in the SELECT. Here we are just counting the InterfaceIDs as all interfaces have one, and filtering where the…

You will be calling the ForecastCapacity table for this and you can use the DisplayName column. Below is an example of omitting any Windows volumes starting with C: Nodes.Vendor = 'Windows' AND ForecastCapacity.DisplayName NOT LIKE 'C:%' You can add additional drive letters on if you want to omit more. For example the…

This is, unfortunately, a Windows issue for which I don't believe there is any current fix. In the Registry of a Windows 11 machine it still shows as Windows 10. If you go to this registry key on a Windows 11 device, you will see that it still shows Windows 10. - Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows…

You could create an Application Template with a Windows Service Monitor component monitor to monitor the agent service then apply the template to all nodes with an agent polling method. I believe the Net service name is 'SolarWindsAgent64'. From there, it will collect the CPU and memory utilisation, and some others, of…

If it's exponentially growing, I'd suspect perhaps something could be wrong with the Database maintenance task, which runs every day to purge old data and merge historical data. In the SolarWinds Web Console, if you go to - Settings > All Settings > Database Details > Database Maintenance - this will show you the last…

I'm glad you found this it was going to be my next suggestion! Just be mindful, I believe this will cease polling during the maintenance period completely rather than just mute the alerts as it is unmanaging the nodes, but if it still works for your use case, then that's great! :)

I believe a maintenance schedule is what you are looking for. With this, you can specify a time that certain nodes are put into maintenance mode. During this time, alerts will not trigger for specified nodes. You can find out how to do this with the following…

I'm not sure if you have SAM in this instance, but technically, there could be some kind of SAM script monitor that executes polling every 10 minutes for that node. See if there are any application monitors applied. Apart from that I can't recall any other SolarWinds function using SSH aside from maybe VNQM

A few Questions spring to mind: * During the migration, did you change the Hostname of the server? * When you look in the Engines table, are there any old or stale entries? * And lastly, in the NetPath_Probes table, are the probes assigned to an EngineID that no longer exists?* i.e., does Probe A have a number in the…

For Windows servers, I would usually recommend an agent just because this can perform polling independent of the SolarWinds polling engine and continue to perform polling for some time should a connection be lost between the endpoint and the SolarWinds server. It will also be better from a security and authentication point…

If this is NPM, first thing I would check is in list resources. How is the server Status and Response time being monitored? Depending on if this is monitored via ICMP, Agent or SNMP, it raises different things to look into

What an awesome response! Thank you @"kellytice" , I will give this a go and let you know if I am successful or not.

Hi @"dgsmith80" , I think I have created what you need. The following SWQL query will look for any nodes in the last 15 days where Logging is enabled on them and they have not received any logs. If a node has logging enabled but has never received any logs, the LastLogDate column will show null next to the node SELECT…

I agree with everything @"shuth" has said, but there is one more Gotcha for the 2024.1 version. Port 17778 was historically used for the SolarWinds REST API. However, this has now been moved to 17774 on 2024.2. Note that Agent-initiated communication will remain on 17778 If you are using anything custom to leverage the…

@"sw_raptor" Hello there! Sorry if this is too late, but as of 2024.1, to make a High Availability FIPs complaint, SolarWinds changed the algorithm for BIND DNS from SHA1 to MD5. However, Infoblox BIND DNS only supports MD5 and SHA 256. There is a workaround for this: Workaround: Replace the newer…

If the SolarWinds log services are running and you have confirmed that the packets are reaching the SolarWinds server on port 514 then there's a very high chance something is blocking it once it gets to the server. I know you said that there were no rules blocking it on Windows Firewall but are there any rules allowing it…