chucksimalchik ✭✭✭✭✭

Bump. Why this isn't a bigger deal for more people, I'm not sure.

Q3 still a problem? Finally getting around to it, then read the thread and see a bunch of back and forth?

I see in release notes for 2025.2.1 a fix regarding the connector update process. Can anyone confirm this fixes the issue I detailed above? 01897353, 01947364The connector update process now automatically updates connectors as intended.

Not that I've dug into it in great detail, but I do have a similar monitor in place and what it SEEMS to be is that on the PID level it keeps the metrics separate, visible on the application details page, but if I map it on a Perfstack chart, it appears to aggregate it to a total CPU of all processes.

Thanks!!! That was the root cause. Appreciate it!!!

We've had a few excellent and some extremely disappointing support experiences over the years. Thwack is often the best way to find a solution.

Very true. This isn't intended to be permanent but a proof of concept with existing processes while some corporate I's get dotted and T's get crossed. The end state will be A directly to C.

Never mind. Allow Node Management Rights did the trick.

Sort of glad to know we're not alone in having seen this. Did you or your enterprise see this only on SolarWinds servers, or also on any other servers? We only saw it on our Orion MPE, but so many other tools are time dependent, As we haven't seen it elsewhere (yet), wondering if it is something within Orion itself that…

Thanks. The VMs in our environment are set to only sync on startup, "sync periodically" is disabled. The systems themselves sync with our DC's, and none of them changed, nor did any of the other systems. Just the Orion main polling engine. Barring any other info we disabled STS and are now crossing our fingers that this…

Sorry but I have not. Haven't dug into it in a bit as we got the information otherwise. We've since upgraded so it probably is worth checking again if behavior changed, but not optimistic that it did.

I've got a similar query (limited to muted alerts) displayed in a widget instead of a report, that some users can't see. I've got a feeling it is related to the AuditingEvents component, but can't pinpoint. The users can mute/unmute alerts, but can't see results of this query. No account limitations are in play for any of…

I use this as a base to find where specific applications are deployed. Could also change the WHERE clause to search for component names instead. Alternatively you can construct it using Orion.APM.Application but this works for me and seems like it would get you where you are looking to go. SELECT…

I've gone down that road but can't come up with any way that didn't involve branching out to some external code or program like TreeSize. If you had several likely suspects, you could tie a SAM monitor with it using the Directory Size component monitor, but you'd have to explicitly define which one(s) you wanted to look…

For what it's worth: support.solarwinds.com/.../Disabling-Google-Tag-Manager-GTM-in-Orion-Platform

Having this show up for all users of the product without any sort of change notification to admins should never occur.

The reason why is basically what @"msites" said. 2020.2.6 has been solid for us, so until the more "modern" releases get more acceptance in the community (and by their nature, become less buggy and more stable), we're interested in keeping current on what we have for the time being. I've not wanted to get boxed into a…

So what's interesting, taking these fields off of the base Node object (n): I get these somewhat inconsistent results, particularly when looking at node.cpucount and how it is not populated in some cases: It seems there are many factors at play here, but when I include the AssetInventory.Processor values, as in the case of…

Certainly a work in progress but building off of this. I've been working on doing similar validation as you have but want to be sure I'm covering all bases. SELECT n.Caption , n.MachineType , CASE WHEN tostring(n.Category) = '1' THEN 'Network' WHEN tostring(n.Category) = '2' THEN 'Server' ELSE 'Other' END as [Node…

The more I look around, the more I don't know. What of these properties? AssetInventory.Processor.NumberOfCoresAssetInventory.Processor.NumberOfThreads

Well, I found the threshold as it is reported in recommendations debug logging. For CPUUsageMHz and ConsumedMemoryLoad, it is "not higher than 30% during 95% of analyzed time". It is configurable in the Orion Advanced Configuration as OverallocationStrategyUtilizationThreshold.

This does appear to have resolved the issue. Will continue to monitor, but we've retriggered and sent the POSTs off properly formatted with no errors. Thanks!!!

Good catch. This was a carryover from a very old alert and we didn't update this one, and it was staring me right in the face. Seems strange that the original isn't impacted but the repeat is, but software does what software does. I'm testing it to be sure the original and repeat will work as expected now and will confirm…

If your SNOW instance supports it, should be no issue to simply have Orion send email similar to your other apps. As noted, you lose some of the benefits of two-way integration. In our case, we send events from Orion to a third party event correlation tool which opens incidents into SNOW.

I'm doing something similar, though not over such a long time period. Regarding the timing, you can either try increasing the polling interval, so it runs less frequently, and then reduce the number of past polling intervals, or try doing what you are doing with a short interval and looking back many. You'll have to…

Yeah. I think application custom properties will be the way to go. We've got a glut of node custom properties as well, but I've found adding custom properties on other objects (Volumes/Interfaces/Applications) has given us a whole lot more flexibility.

I second the "Custom Property" route. What I did is a little different use case than what you describe, but I set up custom props that indicate whether we want to send email/open incident/notify ops and other props to indicate email address(es)/ticketing groups/etc. Then I built alerts for each of those actions if the…

I had a similar problem specifically with a small subset of Windows Server 2008R2 agents when going to 2021.2.1. Not all, but some. The log kept filling with this error: Nio exception: An exception occurred during the execution of select(): java.io.IOException: An operation was attempted on something that is not a socket…

I make use of that alert structure and found that I had to change the table to CPULoad_CS_cur after one of the more recent upgrades. To be honest over the years the alert was semi-unreliable, but has gotten much better in the incarnation I've currently got running shown below. It doesn't isolate to just agent nodes. Works…

I'm running into this with a different product (BigPanda) as well. I've successfully escaped the "\" in volumes, but am finding other issues with payloads. More specifically, we pass certain Windows Event Log messages over, and the receiving API rejects them. And in reality, there are other messages we just can't control…