Service checking

Hi all!

Currently, we have network service checking implementation as a
subagent. It looks like following: some of the network agents understand
parameters like ServiceCheck.POP3(host,user,password) and return 1 if
service responding as expected or 0 otherwise. Then, administartor can
setup thresholds on this parameter to generate alarms/execute actions if
service stop responding. However, this approach has one drawback - all
threshold violation events will have node with servicecheck subagent as
a source, not a node with checked service. This will cause problems with
correct alarm generation and error handling.
I see two possible solutions:
1. Integrate service checking subagent functionality into server (may be
as a server module).
2. In some way (unclear for the moment) allow to change source object
for threshold violation events.

Any comments?

Regards,
Victor
Received on Wed Jan 19 2005 - 14:37:29 EET