Lofstrand · Solutions Architect · ✭✭✭✭✭

I think the line "AE.AccountID AS [Supressed By]" gives you the accountid. Please also look at this thwack post:

Can it be IPAM that scans your subnets?

Hi, sure thing You can use "dependencies" to have less alerts, showing the root cause better. You can also have another set of alerts that trigger if a certain number of devices on the same site are down at the same time. There are even more options like alert stack and more.

Hi This should work: SELECT n.Caption AS Hostname, i.InterfaceName AS Interface, i.Mac AS Mac_Address, n.IPAddress AS IP_Address, n.MachineType AS Machine_Type ,N.HardwareHealthInfos.ServiceTag FROM Orion.Nodes n INNER JOIN Orion.NPM.Interfaces i ON n.NodeID = i.NodeID WHERE i.InterfaceName LIKE '%WAN INTF%' ORDER BY…

Worth noting is that IIS is moving to 64-bit in 2025.4.x versions. 64-bit most likely will consume more RAM.

Yes you can. Take a look here: Add an SMTP server in the SolarWinds Platform

Hi @Sivaprasad Below is a query I have used for some time. Hope it works out for you too. SELECT N.Caption AS [Node], CASE WHEN N.UnManaged=1 THEN DATETRUNC('minute', ToLocal(N.UnManageFrom)) WHEN ASup.EntityUri IS NOT NULL THEN DATETRUNC('minute', ToLocal(ASup.SuppressFrom)) END AS [Suppressed From], CASE WHEN…

No, you have to add another WHERE clause. You can find all functions for SWQL here: https://github.com/solarwinds/OrionSDK/wiki/SWQL-Functions

Where did you see that error message? Have you checked the log file for that specific business layer? Might show more intel

Wonderful! Thanks for sharing!

Hi Generally all small indexes, say under 10-20 MB, you can just skip to check. They will get a high percentage of fragmentation very fast and it will not affect performance as they are so small. In AppInsight for SQL you can change the size of indexes to check. I suggest changing that to at least 10 MB.

Hi @WinterSoldier This part: WHERE N.CPULoadHistory.DateTime>ADDDAY(-7,GETUTCDATE()) Lets you choose how many days back in time to look for information. Change 7 to 30 and you have your month. Can be more complex also but that's where you change this.

Ok, I get a couple of errors in that second query. The sub part where you use IndexOf, has to have the column named. But, IndexOf is not a valid function in SWQL. See all the functions available here: https://github.com/solarwinds/OrionSDK/wiki/SWQL-Functions

@Sivaprasad I have not tested it anymore as your query is working in my environment.

Is any of the services crashing /stopping? Any notes in windows event log? Sounds like you should file a support case…

Hi @Saravana_SV Can it be maybe that the "tables" Orion.Packages.Wireless.Clients are a bit new. Used to be under Orion.Wireless.Clients. I don't have many clients nor ssid's in my lab but wrote below SWQL query. Can it be enough for you? SELECT Count(W.id) AS Qty ,W.SSID FROM Orion.Packages.Wireless.Clients AS W GROUP BY…

Hi @damon_2021 If you use SWQL studio, you can find all API calls: The pink boxes are API call you can use. Another option to find API calls are to look at the swagger page: https://solarwinds.github.io/OrionSDK/swagger-ui/?urls.primaryName=2025.4#/Verbs/OrionOLMProcessingRuleDisableRule Hope you can create a script based…

Hi @jtp74021 Can it be that you have five different cities that have more than five devices over 500ms? The alert will trigger on ONE of the devices in each city. If you only run a part of the query, in SWQL studio, you will see how many devices you have in each city that has over 500ms latency. SELECT MAX(N.Uri) AS Uri…

I looked at the wrong integration. Looked at Customer Portal Integration. @tobyw_loop1 is correct. The issue is with the new Thwack plattform

…also, I think these lines need an update: From Invoke-SwisVerb -SwisConnection $swis -EntityName 'Orion.Nodes' -Verb 'Manage' -Arguments @($NodeUri) | Out-Null To Invoke-SwisVerb -SwisConnection $swis -EntityName 'Orion.Nodes' -Verb 'ReManage' -Arguments @($NodeID) | Out-Null

Hi @Tempest Nice script you created! Some commands want a URI, some a nodeid. For Unmanage, you should use a NodeID, not URI. If you where to use Mute, then it uses URI. A bit confusing. Here are a couple of examples I have: #Unmanage Node Invoke-SwisVerb $Swis Orion.Nodes Unmanage -Arguments @("N:$NodeID", $UnmFrom,…

How about creating something like this: Instead of setting a fixed level of 90%, I have sett "CPU Load Threshold.Critical value reached" (and same for memory) as the trigger conditions. That way you can have individual thresholds on your nodes, if needed. At the bottom of the alert rule, you see that the condition must…

To the right in the "all settings" page, I have a "log out" button. Can you use that one and log in again later with correct credentials?

Will probably not work with that variable in there. Try this. Changing the alert to a "Custom SWQL alert" on Node and use below query: -- Customizable part INNER JOIN ( SELECT MAX(N.Uri) AS Uri ,N.CustomProperties.City ,COUNT(N.nodeid) as QTY FROM Orion.Nodes as N WHERE N.ResponseTime>500 -- The Response time to trigger on…

Ok, but db maintenance has nothing to do with the webservers.

Hi @Sivaprasad Tried your first query and that seem to work just fine. I'm on 2025.4.1 on my lab.

If you go directly towards one of the webservers, do you still have the same issue? If so it is probably not the LB. Also, the maintenance job that take a long time, makes me think there is a SQL issue rather than the LB.

Hi @j.roman In the new version, 2025.4.1, new account limitations have been added. So I think the new webpages are looking for this value, [UDT.UdtAllowInventoriesAccess]. If the value does not exist it displays the error page. Hopefully, below SQL script will show all user accounts that don't have this needed value:…

Great! Another way is to tweak it right in the database. Seems like accounts with the issue is missing the db setting [UDT.UdtAllowInventoriesAccess] in table [WebUserSettings] I have not tried this but it looks like a solution.

I think that will work if you only have the services on ONE server. But with many, it checks the application on all of them. Not one server at the time. Wonder if you have to create a customer SWQL alert for this one….