Hi,
This is certainly not a feature request that is required, or even necessary in the short term, but something which would have great utility and provide massive added value to AHM....
The problem with any systems monitoring tool is to decide how/what/when to monitor to understand the behaviour of a system. If most people are like me you start with a plague of pings and ultimately work up to more targeted script files.
However most system and application vendors have published "best practise" guidelines on how to monitor systems as well as metrics to gauge performance health.
A good example of this is with Microsoft's Exchange/Outlook. See;
Understanding Exchange Performance:
http://www.microsoft.com/technet/prodte ... cd0b4.mspx
Performance counter definitions:
http://www.microsoft.com/technet/prodte ... 1c61b.mspx
So...how about distributing grouped sets of application monitors, based on best practise guideline and metrics, that can be imported into AHM with the server/system target added by the user ?????
Just an idea but perhaps one to add to the wish list...hell this could be user contributed by the ever growing ranks of the AHM community. There must be a host of experts out there you have done this very thing
Cheers
Fergus
PS Can anyone tell me how to monitor the mood of my boss on a Monday morning? I'd pay hard cash for that one.
Preconfigured Application Monitor Group tests
Sorry, that was me just above....
Must remember to look at what I am doing!
Cheers
Fergus
PS on the Exchange 2003 performance counters I mentioned above, have a look at;
"Client Latency
The latency of MAPI/remote procedure call (RPC) actions measured at the LoadSim/Microsoft® Office Outlook® client. This counter measures the time it takes for the server to fulfill the client request. It can be used to estimate the time a user would have to wait between initiating individual Outlook actions."
I've found this is probably the only email stat Managers are really interested in.
Cheers
Fergus
PS on the Exchange 2003 performance counters I mentioned above, have a look at;
"Client Latency
The latency of MAPI/remote procedure call (RPC) actions measured at the LoadSim/Microsoft® Office Outlook® client. This counter measures the time it takes for the server to fulfill the client request. It can be used to estimate the time a user would have to wait between initiating individual Outlook actions."
I've found this is probably the only email stat Managers are really interested in.