instrumenting an application in .NET
-
I believe the system.management.instrumentation namespace provides classes to instrument an application. For example, if an application is stopped, an event will occur to get it started.... The problem is how to i determine the idle or unstable state of an application? Welcome any advice
-
I believe the system.management.instrumentation namespace provides classes to instrument an application. For example, if an application is stopped, an event will occur to get it started.... The problem is how to i determine the idle or unstable state of an application? Welcome any advice
G_Zola wrote: The problem is how to i determine the idle or unstable state of an application? Hmm. Do have a separate watchdog application or service? I guess you want to monitor several things--has the application completely crashed (disappeared from the process list), has it gone into some infinite loop where it's no longer handling UI events (maybe your app can respond to a ping from the watchdog app and fails to respond), is it responsive but consuming a huge amount of CPU time, etc. Just some ideas. Marc MyXaml Advanced Unit Testing YAPO
-
G_Zola wrote: The problem is how to i determine the idle or unstable state of an application? Hmm. Do have a separate watchdog application or service? I guess you want to monitor several things--has the application completely crashed (disappeared from the process list), has it gone into some infinite loop where it's no longer handling UI events (maybe your app can respond to a ping from the watchdog app and fails to respond), is it responsive but consuming a huge amount of CPU time, etc. Just some ideas. Marc MyXaml Advanced Unit Testing YAPO
I wonder if there is a built in attribute in system.management which can access the status of the application. So far i have looked into the win32_Process namespace in root/cimv2 in WMI which may have only started or stopped values for the status attribute. Or i will need an explicit timer to poll the application?