Netservices plugin enhancements

Thomas Segismont tsegismo at redhat.com
Thu Mar 7 12:21:25 UTC 2013


Le 05/03/2013 22:17, Libor Zoubek a écrit :
> Hi Thomas,
>
> I like PingService. It's main purpose is to do simple monitoring of
> machines/devices that do not run agent itself. I'd like to use it to
> monitor my network (I am an small internet provider). My network has
> some topology - one device's availability depends on another device's
> availability. My usecase would be adding all 200 PingService resources
> on 1 platform that would do 'the monitoring' and setup availability
> alert on them. But, if one important device goes down, all dependent
> devices goes down as well - So I might get hundreds of emails. My
> suggestion is, to be able to add PingService child resource to
> PingService resource and explain network hierarchy this way. If any
> important device goes down, I should get 1 alert, and child devices
> would go to 'UNKNOWN' state.
>
> What do you guys think?
> Would that be useful for anyone?
> Does it break concept of Platform->Server->Service resource hierarchy?
>
> Thanks
>
> Dne Tue, 05 Mar 2013 16:50:13 +0100 Thomas Segismont
> <tsegismo at redhat.com> napsal(a):
>
>> Hi,
>>
>> I've wrote a blog post on the recent Net Services plugin enhancements[1]:
>>
>> * some HTTP service features were not fully implemented;
>> * the new Port service lets you monitor a remote port for TCP connection
>> * the plugin now has tests and integration tests for all its services
>>
>> Cheers
>> Thomas
>>
>> [1]
>> http://tsegismont.blogspot.fr/2013/03/rhq-net-services-plugin-enhancements.html
>>
>> _______________________________________________
>> rhq-devel mailing list
>> rhq-devel at lists.fedorahosted.org
>> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
>
>

Hi Libor,

As discussed previously on IRC, I don't think allowing Ping services not 
be nested is a good idea.

You could add a CLI script notification to your root node alert 
definition for this use case.

Cheers
Thomas




More information about the rhq-devel mailing list