BaldFeegle · Monitoring Engineer · ✭✭✭✭✭

Turns out just opening a map in Solarwinds will create the necessary consumers and clear the queues.

Solarwinds has identified an issue with pre-staging in v2022.4.1 which they say they've fixed in 2023.1.

I don't think it's the ISO that's pre-staged. When you run pre-staging the ISO is extracted and the update files are stored in C:\ProgramData\SolarWinds\Installers\. From there the files are copied to the other servers. Copying the files to that location on every poller manually wouldn't make a difference, Solarwinds would…

The main reason I want to pre-stage is that 3 of our pollers have very poor network links to the main poller. Last time we did an upgrade the way you've suggested it took 8 hours to push the files out. I appreciate it's an option, but I'd rather pre-stage without upgrading the MPE's first.

I'm doing the update the same way I've done it several times before. It's been fine every time until this one. Pre-staging a centralised update is the best way to manage our infrastructure. Manual updates are an absolute last resort. After mounting the iso and launching the installer I have only two options. 1, Download…

Hi there, I have downloaded the 2022.4.1 installer and that's what I've pre-staged. Our main pollers have internet access and I suspect that the pre-staged files for 2022.4.1 are being ignored on the Updates and Evaluations page in favour of the more recent 2023.1 release.

Thanks for that, unfortunately it doesn't return anything when there are no matches in the data. I modified the select statement to read "SELECT ISNULL(StatusStep, 'No data') as StatusStep" so it should output "No data" if there are no matches.

That'll explain it. Thanks. 

Thanks, that gave me a way of doing it without even having to use SWQL. First section selects the group with "condition must exist" and "alert can be triggered if" left unchecked. Second section selects nodes which have a specific custom property and has the "condition must exist" set to 4h and "alert can be triggered if…

I found this example which I thought I could adapt to fit my use case. This runs fine and returns groups where 5 or more members are down. As you can see it has a subquery. SELECT Groups.Uri, Groups.DisplayName FROM Orion.Groups AS Groups WHERE Groups.ContainerID IN ( SELECT g.ContainerID FROM Orion.Groups g WHERE…

Tried that but it's not working for me. 

(SELECT CONCAT ( ' StepID:', [Steps].[TransactionStepId], ' Status:', [T3].[StatusDescription], ' Step Name:', [T4].[Name]) As Status_Of_Steps FROM dbo.NodesData AS Nodes INNER JOIN dbo.Dependencies AS Dependencies ON [Nodes].[NodeID] = [Dependencies].[ParentNetObjectID] INNER JOIN dbo.SEUM_TransactionSteps AS Steps ON…

For my purposes I need to concatenate multiple rows into a single string. Using FOR XML ('') achieves that neatly in SQL. I've used it before to do exactly that. My problem this time is that I want to include the DisplayName property in the alert, because that's the name of the failing step, but I couldn't work out where…

Setting up an alert for WPM transactions, but due to the way the ticketing integration works I need to bind on the node. I also want to include in the alert text which transaction steps have failed, but due to another limitation in the ticketing integration I can't pass across multiple rows, so need a way to output several…

Thanks Christopher. I was just about to implement that but decided to have another root around the Trigger GUI Turns out it is possible in the way I was looking for, I just hadn't spotted it. For the scope of the alert I set Node.Node Name = the uri & Component.Statistic Data Label (Multiple Statistic Data) = Response_Time…

Any luck finding a fix?

Cheers @"jm_sysadmin", that was indeed the problem. Much appreciated.

Yes it will, you might experience performance problems but it'll all work together on one server.