Best way, use SiteScope and it’s ability to grab all of the stats during the test. It can grab all of the same data elements as vmstat and needs to leverage a SSH connection through the firewall, which it sounds like you might already have if you have terminal access. 8.x and above you get 500points of SiteScope with your LR purchase for monitoring foundations.
You would think that you could just open up the database and just start bringing in new elements to the [datapoint meter] table along with its associated tables. There are so many relations to manage that the import using that model is cumbersome and prone to error. If you’re using SQL Server as a backend and you are in a location where the laws allow for the exploration of the behavior of a system for integration purposes then you may want to examine the query logs on SQL Server for the queries used to import the data through the analysis tool to see how you might automate the direct import into the backend data store. You need to be real careful on jurisdiction on this one. As the EU is a bit more liberal on examining the behavior of software for integration purposes, in the US that tends to run afoul of reverse engineering provisions of a license.
I well understand your pain on the multiple external file front. At one of our clients we have some machines that we monitor indirectly. We use a mechanism similar to yours involving VMSTAT with the logs directly output in the CSV format at the time of collection, avoiding the perl step. It is still a manual pain to import each one however by host. It would be nice if future versions of the import allowed for a single field to define host. Then we consolidate files for a single import versus multiple imports.
I would press for SiteScope with the SSH access for the time savings (and bill savings) issue for the client. Barring that, hire an intern at a really cheap rate to do that grudge work. Or, chat with your lawyer and accountant about the business value of a Christmas shopping and engineering trip to a location with a bit more liberal laws on examining behavior for integration purposes ;)
James Pulley, http://www.loadrunnerbythehour.com/PricingMatrix
--
You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en
You may want to take a look at birt - http://www.eclipse.org/birt/phoenix/ - as a way to do the things you'd normally do with the analysis tool. It accepts csv files as database sources and can generate some really nice graphs.at the very least they look better...
Best way, use SiteScope and it’s ability to grab all of the stats during the test. It can grab all of the same data elements as vmstat and needs to leverage a SSH connection through the firewall, which it sounds like you might already have if you have terminal access. 8.x and above you get 500points of SiteScope with your LR purchase for monitoring foundations.
You would think that you could just open up the database and just start bringing in new elements to the [datapoint meter] table along with its associated tables. There are so many relations to manage that the import using that model is cumbersome and prone to error. If you’re using SQL Server as a backend and you are in a location where the laws allow for the exploration of the behavior of a system for integration purposes then you may want to examine the query logs on SQL Server for the queries used to import the data through the analysis tool to see how you might automate the direct import into the backend data store. You need to be real careful on jurisdiction on this one. As the EU is a bit more liberal on examining the behavior of software for integration purposes, in the US that tends to run afoul of reverse engineering provisions of a license.
... Then we consolidate files for a single import versus multiple imports.
If such a tool was open source we would not be held back by the speed at which HP chooses to catch up..
In the best of free market opportunities, you have found a need and I encourage you to begin such a project.
Replacing one piece at a time works. Add birt to this and we have the analysis piece sorted. Integrate that with jmeter or some other decent tool for the scripting part and we might be getting somewhere...