In article <BECE02DF.2B40%net>,
Kevin Campbell <net> wrote:
Traditionally, collection of application usage data is done by process
accounting. That's a _big_ disk space strain. If you have the local
disk space on every machine to accommodate this sort of data collection,
Otherwise, I think you're going to have to come up with a set of "jacket
scripts" that instrument the data collection for a selected set of
applications and deploy those on each machine. Then you can build
whatever tools you like based on what information you collect.
What you're asking for is usually done by the OS with very little
granularity. The fact that there's multiple platforms involved
complicates your requirements.
But I have a question for you. Can you cope with the huge information
influx this will cause? What about data retention and archival of it?
What types of metrics are actually being requested that's driving this
request (sounds like an upper-management type reporting project)? In
any case, this may be a case of you having to 'roll your own' system to
collect the data and report on it to your management's satisfaction.
Good luck with that...
DeeDee, don't press that button! DeeDee! NO! Dee...