incubator-s4-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aimee Cheng (JIRA)" <>
Subject [jira] [Commented] (S4-65) Create s4 status command
Date Mon, 09 Jul 2012 03:25:33 GMT


Aimee Cheng commented on S4-65:

For monitoring, the metrics considered to be provided as follow: 

    basic metrics (APP/PE/PE instance): 
         - event rate
         - event processing time
         - event queue size
         - number of PE instances
         - number of processed events ( maybe within a sliding window)
         - exceptions during event processing 
         - actor nodes
        - APP: PE types
        - PE: keys
        - PE instance: key, TTL, survival time and other informations.

We'd like to use Codehale's Metrics( to measure these metrics
in S4. By Metrics, the results are visible via JMX, HTTP, and also can be easily exported
to many other monitoring tools.
> Create s4 status command
> ------------------------
>                 Key: S4-65
>                 URL:
>             Project: Apache S4
>          Issue Type: Sub-task
>    Affects Versions: 0.5
>            Reporter: Matthieu Morel
>            Assignee: Aimee Cheng
>             Fix For: 0.5
> We should have an "s4 status" command that provides nicely formatted information about
the state of S4 application coordinated through a given Zookeeper ensemble.
> In particular:
> - which applications are deployed
> - on which S4 nodes these applications are deployed
> - how many S4 nodes are running, how many S4 nodes are in standby
> - which streams are published, which applications are connected
> The implementation would probably add a new class in the s4-tools project.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message