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

When we went up to 2025.2 there was an issue with agents not fully updating which had me baffled for a while, trying various ways of remotely restarting agents which didn't seem to work because the agent was in a half-conscious state and didn't appear to be connecting. The thing that fixed it was restarting them from the…

It shouldn't do that, it should be displaying the SAML/Entra group you belong to. We use ADSync so our users/groups are in AD but sync'd to Entra so when we log in with SAML we get the group name our accounts belongs to. How is your authentication done?

I liked this change, because in the past when someone did something mad like use a personal account for customer monitoring they would ultimately change their password and monitoring would silently fail but the node was still Up because ping. Occasionally I'd be looking through the logs for a different polling issue and…

We should all get notifications when it's down

What polling method are you using? Are Prod and Dev in the same subnet? I had a beauty last week that was the same issue; turned out that one node was in the same subnet as the poller and there was an any-any rule on the subnet so pinging worked, but for cross-subnet there were Extra Rules that needed to be added.

I've done it for our API pollers in Classic Dashboards by adding a Custom Table widget and configuring it with a SWQL data source that pulls the API poller metrics directly from the Orion.APIPoller.ValueToMonitor table. For Modern Dashboards your widget does a similar query but without the HTML, then gets formatted.

That's exactly how we did it. It's not ideal and you get high latency but it works. Make sure you're using asynchronous replication for the Availability Groups.

We just built Windows VMs and installed the software. Manually build SQL cluster for the backend. Pay attention to the server and port requirements and you shouldn't have an issue. For app upgrades you make sure the VM is backed up, then snapshot the OS disk and do the upgrade. For Windows patching use the Azure Update…

I'd recommend reading this Solarwinds document on how to do this. Deploy SolarWinds Platform products to Microsoft Azure We're running our entire SWOSH platform in Azure and the only thing I'll say is make sure your backend SQL server(s) are very highly spec'd otherwise you will have bad latency issues. Follow the Azure…

The network collector is showing as critical, not down. How's it doing for performance and RAM usage? You can also check the collector health in the SaaS portal and optionally download logs, though sometimes I find it quicker to run the diags on the mpe/NC and look through those instead.

How are you deploying from the node itself? Outbound deploying from the Primary Poller needs port 17790 open as well as others for agent transfer etc. Here's the list of ports required for Agents: SolarWinds Port Requirements You don't normally have to do anything with the certificates.

Orion.APIPoller.ValueToMonitor is the base table for poller information. If you look at its declaration in SWQL Studio you can see that it links to both Orion.APIPoller.APIPoller and Orion.APIPoller.ValueToMonitor.Metrics and these are where the polling results are stored. This is a widget query I wrote for testing whether…

That should be laid out as one large OR block with the three AND blocks within it, so: (OR) (AND) (AND) (AND) This means any of the AND blocks can trigger the alert.

Never mind, I got there in the end, but it's very restrictive. The parameters are actually the Solarwinds implementation of the Handlebars.js template engine, but utilise more of the backend which is Mustache. Introduction | Handlebars Unfortunately, because Solarwinds uses the Mustache backend there is no logic possible…

I'm guessing you're not using HCO SaaS because database analysis is built into that. For other platforms there's DPA - Database Performance Analyzer (DPA) | SolarWinds

You can't yet, but it's coming hopefully this year thanks to a platform migration to .NET 8.

As far as I'm aware you can't. I've asked this question before.

Apologies for the scrappily formatted query, but this digs out that info. I've not worked out the significance of the 'enabled' column yet though, it's showing some of our nodes as disabled but looking at the List Resources it's very much active. SELECT p.PollerID, n.Caption, p.PollerType, p.NetObjectID, p.Enabled FROM…

Run the Config Wizard on your new primary poller. Assuming you've copied the old DBs to their default locations on the new SQL server then the config wizard should pick them up. The 'Migrate' link dodo123 posted is worth reading too. Using the same hostname as the old server is recommended. You shouldn't have an issue with…

Success! Kind of. Using the SQL Profiler I tracked down the actual query the poller was using to capture the node data and sent it to a colleague who's SQL is far better than mine. He said that a LEFT JOIN I'd used would work better as an INNER JOIN so I changed the query and lo, the blank lines and dashes went away and I…

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.