Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Monitor multiple processes

Does anyone know how to monitor the CPU and Memory utilization of multiple processes? We have 12 copies of the same process running on our servers (on purpose). We would like to know which of the 12 has gone haywire and track it's usage so we can go back and determine when it got crazy. For example sometimes a single process will have a memory issue and start using 10x more memory than normal.

Find more posts tagged with

Accepted answers

VáclavSáblík

After some digging I find out that trigger condition works well but there is a problem in reset condition when set to "Reset when trigger condition is no longer true". In some cases it behaves differently than is should.

There is a workaround to set reset condition manually. I updated original post with reset condition.

Sorry for inconvenience again I hope this time it will be working alright.

Note: This will not affect options 1 and 2.

Thanks,

All comments

martin.susil

Do those processes have a different command line parameters? If yes, then you could use 'Command Line Filter' setting when editing component options to specify which instance you are interested in.

MrSampsonite

Not sure I know what you mean. We start a service for our application and it in turn starts 12 instances of this process.

martin.susil

I mean command line arguments like

c:\process.exe /some_specific_argument_to_identify_instance

If there is no specific argument specified, then it's not possible to distinguish various instances from each other (between polls). Because when process is restarted, it gets a new PID and it's not possible to match it against historical data from previous polls.

MrSampsonite

I'm ok with not being able to detect historical information. All I need to monitor is the following:

1. Are there currently 12 instances running. if not I need an alert

2. Are any of the 12 using over XXX amount of Memory or above YYY CPU utilization

3. If possible, are any of them restarting (different PID than before).

Number 3 may not be possible but I'd be happy with numbers 1 and 2.

Maybe some sort of script could do it?