Comments
-
Without the historical data, the waterfall servers no purpose. We need to be able to go back in time to see what component on a page caused slowness, or didn't load.
-
How is the licensing to be handled for MySQL instances?
-
It is. WPM 2.2 has been GA for several months.
-
The event timestamp is in UTC. The last played timestamp is in your local time. This has been an issue for a time.
-
I believe there is a hotfix available in the customer portal that will fix your issue bbrown51.
-
I have this requirement too. We are using scripts to get the counts today.
-
Our NOC uses the widget pictured above for all searching. The useful seaches built in SAM/WPM are part of the admin pages which very few people have access top.
-
Great new features. The conditionals are great. Much needed for a long time. I think the positive/negative matches will be useful too.
-
Pingdom has not been integrated into the Orion platform. I could speculate that WPM is being replaced by Pingdom tech since WPM has been all but abandoned since the purchase of Pingdom.
-
Our company is prepping for proof of concept testing of a large number of Orion modules. Unfortunately WPM will score a zero on the "Support" and "Customer Relations" area's before the product is even installed. I previously managed a large Orion install at another company and the lack of WPM updates, support, and…
-
"We also improved the WPM Player and Job Scheduler, which are now more intelligent and jobs are scheduled in smaller buckets, more evenly distributing resource usage.". Does this mean that each player will be able to handle more transactions? Player scalability is a huge issue for my team right now.
-
wmi process monitor, use w3wp.exe as the process name, and the app pool name in the command line filter.
-
Great article!
-
I'm talking about the URL sequence monitor in SiteScope. I monitor hundreds of web sites with this type of monitor. A typical deployment would be to use BAC for the public facing side of a clustered web site(BigIP). We would use SiteScope(URL sequence monitor) to hit each nodes web site using it's private address.…
-
I don't like the idea of a sequential playback instead of parallel since it won't scale. I do see that many of your transactions talk a long time to execute(30 + seconds), and not knowing the actual amount of rendering needed for each transaction I can't say I disagree with the sequential approach. I've had to code a…
-
The username is v3get. It's near the top of the snmp help on the IronPort. Very easy to miss. Select MD5, then enter the password you added using the snmp config on the IronPort. Select None for Privacy / Encryption.
-
I'm talking about the URL sequence monitors and the soap monitors. Seum 200 is still more expensive(about double list price of SiteScope) and less functional than SiteScope with 200 point license. If SEUM could re-record scripts or allow script editing, it would be a passable solution. SiteScope allows steps to be…
-
On the monitor view, click on the radial CPU image(normally in the upper left corner) to start the drill down. To the right of "Adjust Time Period for Chart" select your time period, or optionally enter a start/end date range. Next Select your sample interval. Click the refresh button. This will display the historical CPU…
-
So did you change your polling interval to 10 minutes?
-
We don't get them daily, but it happens more often than it should. Usually after the core is having issues, or gets rebooted(for patches). Almost all of the time testing the player will cause the transactions to start playing. This has been an issue since WPM 1.0.
-
Can you provide an example? I've added the DLL's to a new project and not making any headway.
-
Eaton Poweware Universal Device Poller
-
APM and SUEM don't compare to SiteScope in terms of simple web site and web service monitoring. APM doesn't do much beyond a simple form post for web sites, and you have to use powershell for web services(takes too much time if you have a lot of web services). SEUM can monitor web sites but is too expensive for simple web…
-
Not that I'm aware of. Fingers got pointed in both directions.
-
The roadmap is still missing...
-
299534.
-
The scalability leaves a lot to be desired. Our old website monitoring tool, HP BSM/BAC, could handle several hundered transactions per player. We bought WPM to save money, but in the end it will cost more because it required more players, and therefore more servers.
-
You can also try clicking the "Test" button on the "Edit Transaction Location" form. For some reason this usually fixes the issue(since WPM 1.0).
-
The NPM "Memory Used" is not Physical + Virtual. It's physical only. It SHOULD be Physical + Virtual.
-
Ditto on the audit trail!