jbiggley ✭✭✭✭✭

To support that tweak to the query I was doing some testing today using my last 4 hours query and I found a fatal flaw. In *some* cases a server may not see activity on all processors in the previous 4 hours. Why? I'm not exactly sure. It could be a poorly coded application, a CPU pinned process, etc. Regardless, when we…

Alex, sorry -- bad writing skills are to blame. There are two conditions that must exist. First, VMs must be managed nodes in NPM and second, in a multi-poller environment IVIM needs to have both hosts and the vCenter that manage them assigned to the same poller. If you only have a single poller then you can ignore that…

I should also add that we found some of our custom-tuned entries in the SWNetPerfMon.db file in our \SolarWinds\Orion directory. Because we have such a large environment we modified this file (on the advice of support and the devs -- DO NOT CHANGE THIS WITHOUT TALKING TO THEM!) to ensure that we can talk to the DB without…

Thanks for the response. I'll get our development team both options as getting access to the LUN data would be preferable, though using our Orion SQL DB would be a lot easier.

That was the trick Lukas! The local admin account that I use to log into the web console (not the individual appliances for administration via the :5480 page) worked like a champ. Domain account definitely did not work though.

Oh man, typing fail. Sorry, updated the version to correctly state 1.9.137.0. I am running the latest/greatest.

What if we *like* the bug?

I knew we three were kindred spirits -- awesomesauce is my go-to exclamation too! You, Leon Adato and I would be dangerous together.

Awesome! Yeah, I'll open a case for sure. Figures I did something wrong, eh?

Nice, if you have SAM at your disposal We ended up using a combination of warning alerts and the hrsystemuptime OID for monitoring when a server actually reboots. Warning alerts give us a pre-emptive view of nodes that might be transitioning from up to down and the server hrsystemuptime OID lets us capture the actual…

Yeah. The query works fine in SSMS it definitely looks like the web-based report builder that is causing the problem. It feels like it isn't truly replicating the functionality of SSMS from a query perspective.

lukaseko Is that Base Filtering Engine on the dedicated NPAS server or on the additional polling engine that it is pointed at? What are the implications for other products if it is on the polling engine? We have NPM, NTA, SAM, etc. in our environment all running on that same additional polling engine. Thanks

Curious as to what "one or two orders of magnitude larger" means We have 18 pollers across 3 data centers, 11000 nodes, 75000 elements, almost 100,000 application monitors. Running NPM, SAM, VMAN, NTA (kind of) and just purchased STM/SRM. Is it that kind of big? I ask as the impact of a botched upgrade on a single poller…

I know that I am responding to a *very* dated note, but this query is limited by your data retention settings. By default it is 365 days.

I appreciate the pointed assistance -- especially to this accidental DBA. I'll let you know if things improve.

Agreed. I suspect that the exact tactic you just outlined could be employed in other places in the Orion suite to limit the impact to the core SQL DB. I guess we'll have to wait and see what the future holds for us. That said, this is the era of big data. Converged (aka Single Pane of Glass) views of disparate data sources…

Replace the script body with the following code. The code you have posted in the script block will not execute. It needs to a properly formatted PowerShell script or command. Let me know how that works for you. $process = Get-WmiObject win32_process -ComputerName '${IP}' -Credential '${CREDENTIAL}' | Where-Object {$_.Name…

So I did some more testing. This appears to be either an AWS ELB fail or an ELB configuration fail. I flipped the AWS instances to SNMP and verified I could connect from the polling engine to the instances without issue. Remember, I am using the same security group for the ELB as I am for the instances. I also added an…

you totally did everything the same way that I would have. Well that's the best compliment ever! I'm going to flip those nodes to SNMP or WMI and see if it makes a difference just to make sure it isn't some oddity, but I agree -- this certainly seems like an ELB oddity.

Simon, looking at the case notes it appears that I resolve the case with SW support without a resolution, but I can tell you that the data is being collected today. Are you running the latest/greatest NPM including both HF1 and HF6 (they are separate HFs -- HF1 makes QoE/DPI licensing free but HF6 has a dependency on HF1…

Hmm -- give me a bit. I'll see if I can dig up some more detail for you next week. I don't know about the 4G but I can tell you we aren't transforming that data at all.

Depending when you called, you definitely could have ended up in Singapore or it could have been via overflow. SolarWinds support uses a Follow The Sun model for support so you will encounter folks from all over the world. If only I could figure out how to make my technical problems happen during 9-5, M-F Eastern time.

Any luck on confirming if this value is available via 5.1 chrispaap? I don't have access to the hosts myself and I'm trying to track down a VMware resource to help. You might be quicker though

Yes, there is a memory leak in the SWISv3 service that usually only surfaces in large environments. It will be rolled up in HF6, but there is a buddy drop available to fix the issue immediately.

Just an update that we saw this error after upgrading NPM 11.0.1 to 11.5.2 with an additional web engine on a separate server. The exact error is below. An IISreset on the additional web server fixed the issue. Interestingly, this only happened on the additional web server for us. If you connected to the primary poller…

No, unfortunately not. The widgets for Orion naturally connect only to the Orion DB. The inability to execute a SQL query against a non-Orion DB was the first problem, but being able to pass a common identifier was the second, and perhaps more challenging, problem. For example, if the SQL query was to use the IP address of…

Check your C:\ProgramData\Solarwinds\Logs\Orion\swdebugMaintenance.log file and make sure that maintenance actually completed. Also check your C:\ProgramData\Solarwinds\Collector\StreamedResults directories as well as Server Manager > Features > Message Queuing > Private Queues to make sure there aren't any backups there…

No, that's why I am passing the credentials to the Net-Object cmdlet. I want to use the credentials that SAM has stored to execute the test on the polling engine.

Re: Passing ${CREDENTIAL} in a PowerShell without using -Credential That was what I did. It works locally on the polling engine but does not work via SAM

It is a local user, no domain.