Best Practice: Windows service monitoring

[schaf.mh]

Hi All,
I'm planning to implement a feature for a system in a windows service that different applications can take advantage out of it.
I'm not the windows service specialist but I would like to have kind of a monitoring and controlling possibility of my service.

I would like to see the amount of connections, space used and requests queued and other similar stuff. My plan is to configure the limits of the some monitored 'attributes' and do actions for that. Kind of alerts. (e.g. sending emails or increasing the log level)
I saw that there exist a lot of open source tool where I can monitor some settings of a service, but I also would like to influence the behavior depending on an alert. E.g increase login details or reject connections if less the 5% of memory is available.

Is there kind of a best practice or a pattern how to implement a service like that? Does .NET have a library or similer for that?

Thanks
Marcel

 

[Arne Vajhøj]

Hi All, I'm planning to implement a feature for a system in a windows
service that different applications can take advantage out of it. I'm
not the windows service specialist but I would like to have kind of a
monitoring and controlling possibility of my service.

I would like to see the amount of connections, space used and
requests queued and other similar stuff. My plan is to configure the
limits of the some monitored 'attributes' and do actions for that.
Kind of alerts. (e.g. sending emails or increasing the log level) I
saw that there exist a lot of open source tool where I can monitor
some settings of a service, but I also would like to influence the
behavior depending on an alert. E.g increase login details or reject
connections if less the 5% of memory is available.

Is there kind of a best practice or a pattern how to implement a
service like that? Does .NET have a library or similer for that?

I don't know what is best practice.

But I would let the Windows service expose a management API
via remoting.

Arne