#Pinpoint pro errors how to#

And we couldn’t figure out how to zoom in on NetApp’s software. Sure enough, if you aggregate the 8pm hour, you get 1350. I ask him to look at the next data point…800 IOPS 11pm. “But Balancepoint says I got 1350 at that time!” So, I ask him to open it up, and sure enough, 1350 9pm. Sure enough, March 1st 8:30 pm, 3,500 IOP spike. Then I look at the volume IOPS report on the NetApp, during the same timeframe. Customer then realizes the original number of “55,000 IOPS” probably is not real in his specific setup. A quick calculation later, I estimate about 3500 IOPS total. Next, I go into the NetApp, look at the RAID report to see how many IOPS he can do. I go to the storage tab and go into Logical mapping, find which LUN and aggregate it belongs to. Ok, so, I go into SolarWinds Storage Manager, hit search in the upper right, find the VM with the component in question. “But this VM is backended by a NetApp!! It can do 55,000 IOPS!!!” Yeah, I was suspicious at that, so, I asked them, “ok, do you have Storage Manager (STM) or another storage monitoring product installed so we can check?” Sure do, and he promptly informed me that NetApp’s Balancepoint was telling him that while he averaged about 860 IOPS per day, during that hour he spiked to 1350 IOPS, still well within his supposed “55,000” IOP limit. I’d seen this before, and it always relates back to the disk. The component in question was actually from the Windows 2003-2012 Services and Counters, specifically “Pages/sec” was going critical. The following is an actual description of a discussion one of our engineers, Matt Quick, had with a customer as told in his words.Ī customer using the product evaluation copy of SolarWinds Server and Application Monitor (SAM) called us wanting an extension on the trial because “SAM was broke, keeps alerting a component when we know everything was fine.” I asked to take a look at the customer’s historical data.

Pinpoint pro errors