fop · 3rd Level Techromancer · ✭✭✭✭✭

The plot thickens. For a SYSTEM Modern Dashboard like the Vulnerability and Risk it works as expected, but the second you unlink the SWQL queries to create a modified version of that dashboard the account limitations are ignored. So I'm back to square one trying to get the limitation of the logged in user so I can apply it…

OK, I set up an identical account limitation in my homelab and it looks like it does actually work properly in 2025.2 - one team sees 'their' nodes and the other team sees their own in the Vulnerability Dashboard. I guess that's the final push I need to make me get that upgrade scheduled! Cheers

This was the conclusion I ended up at yesterday, so I set about trying to work out how I could grab the account limitation of the logged in user and apply that to the custom property in the SWQL or use on a global filter. It seems like I can't get info of the logged in user because that just isn't stored anywhere, but…

My main one is increased RBAC so we can have utterly non-priv'd users (customers) being able to view their own estates. There are workarounds for this. I realise this might be kind of difficult for a product that isn't designed to be multi-tenant though. SSO auth for SWQL Studio. Currently I can't let my users access it…

We had this issue on 2020.2.6. I've not done much with Custom Properties in the current version we're running but that doesn't mean the issue has gone. Support and the devs worked for months on it and all we could decide was it was to do with IIS caching. If you restart IIS do the property changes show up? My homelab is…

That's pretty cool, thanks for sharing! The log locations will be handy too, I'll add those to my 'useful SW directories' list.

If you rely on Azure Cloud Monitoring then I'd stop at 2025.1 because all later versions have a bug that prevents cloud monitoring working correctly due to SW not handling a paginated response from Azure correctly. Your monitored cloud VMs will literally disappear and can't be re-added. As of 2026.1RC this is still true.

Hey Kevin, nice to see you still around :D I've learned a lot of things from your posts and articles, only still a n00b myself since I only signed up 3 years ago. Here's to another 17 😁

Proxmox Cluster support was added in 2025.4 which is currently in Release Candidate testing. Note that it's expecting a cluster - single node monitoring is via SNMP as @naveensingh43 says, or you can install an Agent on your VE server. This is how I'm monitoring my lab but bear in mind you can only get server telemetry and…

Cursed alerts overnight, woe. Red icons on screen - help me Boss unhappy, need green.

Hi Kevin, nice to be visited by an Actual SolarWinds Person :) The reason I created this request was that I was investigating non-standard SolarWinds API pollers, in this case the Azure Application Gateway. Using the MS docs and an initial script for authentication from someone here I came up with a script that worked…

I did try getting SAM to execute pwsh but not in the way you're doing it there. From a PS5.1 window my script worked fine, but I couldn't get it to play nice in SAM then ran out of time.

When we took on a load of Dell servers for HW monitoring I was amazed to find that they just don't exist in the Orion world. As a purely HPE house previously we had the luxury of iLO integration which is an excellent thing.

We have had someone desperate to back up their workstation because their monitor was on fire. That was a fun call.

Congrats everyone, and greetings all. May the next 12 months be very Solarwindy.

I was talking about this in a meeting just yesterday, much more useful than a page of numbers.

I came here to ask a similar question, in my case 'are the Dashboard database entities available to a widget', so I could use something like SELECT n.caption as [Nodename], n.IPAddress as [IP address] FROM orion.nodes n WHERE n.customproperties.customer_code like '%${DASHBOARD_TITLE}%' which would mean the dashboard title…

I like the idea of a Cache Blessing Ritual, maybe sacrifice some Thwack points to guarantee that the cache improvements it recommends are watertight.

Bah, the 'tell us' option on today's question didn't bring up a text box, so the answer is: 'A rogue DBA from the TLA department causing a MIM because their IDX was thrown out by a CEO claiming it was SEP.'

...or not. I've discovered that the issue is the 'apma.Components.MultipleStatisticData.NumericData' line so now I need to work out why that's seen as a Bad Thing. I get the same fault if I link into apma.Components.CurrentStatistics.ComponentStatisticData as well. I can get the same data if I go straight to…

Aaah wait, you can expand the fault box AND copy the error to the clipboard, this may help.

We keep OME separate to Solarwinds, and don't do the HP stuff, but for xClarity SNMP is available via the 1.3.6.1.4.1.19046.11.1.1 MIB. I have monitors for the fans in xClarity-monitored servers. Set up pollers in the Solarwinds UnDP Poller config and you can alert on the polled values. Check the documentation here.

Try this. If I was doing it I'd add the 'is not unmanaged' option in line 3 of the trigger scope. I don't have easy access to SWQL Studio right now to verify it but it looks right logically.

Your trigger needs to be an AND block of the 'node' properties - node name, polling status (though I'd change 'status' to equal 'up'), then the 'what fires the alert' block is an AND block of your component values. IF (node name is SERVER001 AND server is up) THEN IF (monitored component is Spooler AND its status is not…

I did think about changing it in the DB, but also thought that might have ramifications. Dammit. Pleased you got sorted though.

As someone who went through exactly this exercise a few weeks ago thanks to a typo on my part when I first created the groups for our new poller I can say that unfortunately you need to create new Windows Groups with the new name once you've set it in AD. What would be awesome would be if you could duplicate&edit groups…

First thing I'd do is open a powershell session and 'test-netconnection -p 17778 <poller>' to see if the server can contact the poller. All the logs for the agent are in C:\ProgramData\SolarWinds\Logs\Agent, so if there's any errors to be found they'll be in there.

Yep - AppInsight for SQL requirements and permissions

We have this issue on 2023.3 too, and I *think* it's because SW will attempt a logon with the machine account before trying the account it was configured for when you ran the Config Wizard. Like most folk (I think) we use a single windows account for SQL access from all pollers and web servers, but we still get 18456…

Thanks for the reply. We were waiting to actually get a RRAS server to explore but that's not moving as quickly as we thought. Meanwhile, someone came up with this list of monitorable attributes which I suspect is pulled straight from the Microsoft Documentation. Currently I only have an alert for the RRAS service itself.…