bobmarley ✭✭✭✭✭

Keep up the great work!

Would love to hear more about your customizations@"[Deleted User]" 

Great work! Thank you for sharing.

Thank you for the update!

I agree totally, if you know the credentials and can delete and rediscover that would be the best route as you will be starting off with a clean environment.

I had to readjust the time on all of my perfstack dashboards after the last two upgrades as well. 

You may want to start by running a report showing the IP, Caption, and DNS of all of the nodes in SolarWinds and then running an NSLOOKUP against all of the IP's and see where your discrepancies are and correct them. Once you have all of the names corrected you may want to rediscover all of the nodes and ensure the agents,…

Certifications never hurt. We had to interview many people to fill our last couple of open positions. Certifications would have made a difference in the hiring. 

I checked as well and not seeing it in the downloads area yet. 

Good info to know, thanks @"jm_sysadmin" Thanks @"maliron" for finding it and posting the bug. 

I haven't specifically tried it in modern dashboards and global filtering but for other coding reasons we have always used Street_Address or Location_Name as well as names such as _Ticket_Severity. Have never ran into an issue with underscores anywhere in the tools so if it isn't working it may be a bug?

When you encountered this issue with HTTPS monitor nodes, it’s possible that the license had expired. You mentioned that you’re about to renew it, so that should resolve the problem. If you encounter it again, consider checking the license status and ensuring it’s active.

Here is a similar one for running a Powershell script if you would like to compare syntax. In the example below a combination of double and single quotes is used. The Custom Property that your are trying to pass would also need to be a valid variable name. C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -Command…

I have used underscores in all of our custom properties and have never found them to be an issue. This may be a first. 

Any time! 

Change the Where to this and fill in the items that are all caps. WHERE ComponentPercentCPU >=0 AND s.Component.Application.Node.Caption LIKE '%YOURNODENAME%' AND s.Component.Application.Name LIKE '%YOURAPPLICATIONNAME%'

Possibly try DOMAIN\USER 

Pre 2024.2 Port 17777 was used, beginning in 2024.2 the port was changed to 17774. If you have a current version of SWQL Studio you should be good. If you still can't connect, consider if there are any firewall rules in place that would prevent you. You could test port 17774 from your workstation to the main polling…

Perhaps use a script to count the number of objects then run the script using SAM.

Many medical vehicles have full networks installed including routers/switches because a lot of the medical equipment inside is ethernet connected. We don't monitor them for Up/Down but we do collect SNMP information, Syslogs, and Traps, etc.. Some items include special ambulances, portable CT Scan units, Event bus's such…

Yo tengo VNQM pero no tengo Cisco Cube para evaluarlo. Quizas, haya alguien en el forum que pueda responder. We have VNQM but don't have Cisco Cube to test with. Perhaps someone else in Thwack could assist? 

Possibly try this, not sure it will work. Use this query to find the numbers for the polling engines. SELECT ServerName, IP, ServerType, EngineID FROM Orion.Engines Then include the polling engines in the alert 

SIP monitoring on Cisco CUBE devices (solarwinds.com)

This appears good as it is written, it will apply to all nodes in your network that have the poller assigned to them, and if the current value is less than or equal to 10. That you may want to adjust to = 10 but the rest of the alert looks fine. 

From your error it looks like you are using port=17774 which is the new port. 

Click @"mark.gover" link and then try here 

The API port numbers changed in this release, check out the release notes. 

Check the release notes for your upgrade. Port 17778 has changed to Port 17774. Good chance you are using the old port.

The tables that you are using are already linked/joined. The NPM.Interfaces table -> then go way down to the links The link to the table is named Traffic Perhaps try rewriting the query without all of the joins would allow it to run faster? Below is what query would begin with using the pre-joined links SELECT…

$yourvariable = [math]::round($size[$_] /1Gb, 3)