You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2013/02/19 11:27:13 UTC

[jira] [Commented] (SLING-2597) Provide interface for monitoring services

    [ https://issues.apache.org/jira/browse/SLING-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581195#comment-13581195 ] 

Felix Meschberger commented on SLING-2597:
------------------------------------------

Ok, we agree JMX is the solution. So lets go the full JMX way.

* We expose Queues as MBeans
* We might want to investigate into looking at JMX Notifications
                
> Provide interface for monitoring services
> -----------------------------------------
>
>                 Key: SLING-2597
>                 URL: https://issues.apache.org/jira/browse/SLING-2597
>             Project: Sling
>          Issue Type: New Feature
>            Reporter: Jörg Hoh
>
> There should be an interface which one can query to get information about the status of a service implementing this interface.
> eg.
> public interface HealthCheckable {
>   public int getStatus();
> }
> For the return value for this method we could use:
> static int OK = 0;
> static int WARNING = 1;
> static int CRITICAL = 2;
> static int UNKNOWN = 3;
> (these are the values which Nagios uses as return values for its plugins, see http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN76).
> The decision what value is returned is delegated to the service, so maybe they need to have some configuration to define the points, where a "OK" becomes "WARNING".
> Via OSGI whiteboard pattern we can collect then all services providing status information and calculate an overall status of the system. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira