The requirement is to start many processes and monitor them to ensure they stay running. The process will read a config file that defines a behavior, so the process itself is very much just a template.
So what I need is a container mechanism or a design pattern, but the limitations of the production scenario include....ie they are out of my control,
windows server 2012R2
No Linux
No VMs period
A C# solution would be best, but not required.
Currently I was thinking a windows service that would start and poll, but that seems clunky.
I do not see an event for application crash from the OS and have found a few people say it is not there and that you could hack in looking at event logs... that seems awkward.
Any other good options?
Aucun commentaire:
Enregistrer un commentaire