FormerMember ✭✭✭

This happens in all my application component detail counters, they all have CPU queue length on the right...

Is this just an oversite and will it be put back as a feature or is there a better way that I am unaware of. This is a bug. Thanks for pointing this one out. We'll get this fixed. 

This is a known feature request that we're considering for a future release.

To expand on what Curtis said, it sounds like we just need to glue your rule together. The DS group you could think of as the "right hand side" of a comparison, and doesn't do anything on its own. Looking at the rules, I think it might be hard to do this in one rule because of how the fields lay out, but I'd start with…

NPM 12.2 Release Notes - SolarWinds Worldwide, LLC. Help and Support Adam @acmtix

This is a known issue and a fix is coming in a service pack.

We're looking at this issue now. When we have some more information, I'll let you know.

Bummer, all drivers are up to date, no updates for Windows. I'm at a loss...

I was actually looking at this just recently as part of another case. The second engine appearing as 'primary' isn't a problem. Currently the only distinction that is made in the serverType column is for Hot Standby engines.

Currently, LEM/SAM can share data via SNMP Trap Integration. You can send SNMP Traps from SAM to LEM (or LEM to SAM). For SAM to LEM, this is handy because you can fire events detected by SAM into LEM and they will be co-mingled with other log data for troubleshooting, root cause analysis, and the like. For LEM to SAM,…

Hi Guys, Thanks for the replies. Im currently in the process of trying to update to SP5, however it SHOULDNT be the reason for the error. Clicking on the >> in Node management does not show my custom properties either. I have made some screenshots for you to look at. Country Site and State are there. Country State and Site…

when you add these IPs then the interface you want to select is the MS TCP Interface. then all the information you see will be only for that IP. You should have a node for the physical server that monitors the actual NICs that you can get cumalative info from.

I'm not exactly sure what the problem is, but the first thing I'm going to suggest is installing the latest SP for 9.5. It will be available for download. SP 2 isn't the latest.

Do you have any nodes still assigned to the "ghost" poller? If so, you need to reassign them. To make the poller stop showing up in System Manager, go into the Database and delete that poller from the Engiens table.

We are using SolarWinds NPM and moving to Cherwell. Searching for guidance on integration between the two in order to generate Cherwell tickets from NPM alerts.

your select is only going to get data from the nodes table. You will need a much broader statement to grab all the info you are looking for with unions on the node id to span all the tables. As it is all you will get is data from the nodes table.

It's not at all clear from your description what's going on. I looked at your case, and support provided another response this afternoon, so it's still moving forward. I see that the Support tech is looking at a capture. He's got a lot more info that we have. If he can't help you solve it, it'll go to Dev.

yeah i dont think this has any analytics in it it just extends the line based on averages for the graph you are looking at to give you a feel of the progression

Additional Additional information. I removed a node from monitoring, ran discovery on it's domain, and then checked to see how it appeared in Solarwinds. Instead of using the Agent, it's using WMI. In Sonar Discovery , I selected the option "check for agents...". In then polling method preference setting, you can only…

Is it possible set 1 alert that starts sending every 15 minutes when a node is down.. .then stops sending after a specified amount of time…. Then set a second alert that doesn’t start sending until a node is down for a specified amount of time, and doesn’t stop sending until the node is back up? i.e. Alert 1 sends an alert…

Thanks for the very swift reply. I will try all of your suggestions and let you know on the results.

Oli- this might be a bug with the "starting with " trigger...we've got something very similar, and it works just fine...

It's a known issue. We're working on it. 

 9.1 does not support the double bytes language? Correct. We do not support double-byte languages at this time.

I've also spent a lot of time automating Orion additions in Python, the lack of a number of helpers (like adding volumes) or requiring to know information on the node (like it's type) and then add the right pollers (with Interfaces it's just calling `AddDefaultPollers`) is rather annoying.

Hi and welcome to Thwack! :-) This is a job for IPSLA: a trial of that module will give you the information you need. http://www.solarwinds.com/products/orion/ip_sla_monitoring/

In addition to parent, can I suggest the child be allowed to be an Application/Component etc too. e.g. SQL performance counters template is dependant on SQL process monitoring component.

Try going into the Client section and do a search of the email address only. I have found that sometimes, WHD creates multiple Client profiles and causes this error. In some cases, I found well over a dozen records of the same email address. When I deleted all client records except one, the issue was resolved. Good luck!…

Yes, but keep in mind that APM is searching the HTML, so make sure that the next can be found in a straight HTML search. 

 That message means that the device/interface is not being managed by Orion. Add the node and all its interfaces via System Manager.