[jboss-jira] [JBoss JIRA] (WFLY-5043) Undertow mod_cluster CLI: Display node's Elected, Read, Transferred, Connected stats

[Stuart Douglas (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas moved UNDERTOW-493 to WFLY-5043:
-----------------------------------------------

              Project: WildFly  (was: Undertow)
                  Key: WFLY-5043  (was: UNDERTOW-493)
           Issue Type: Feature Request  (was: Bug)
    Affects Version/s:     (was: 1.3.0.Beta3)
          Component/s: Web (Undertow)
                           (was: Proxy)


> Undertow mod_cluster CLI: Display node's Elected, Read, Transferred, Connected stats
> ------------------------------------------------------------------------------------
>
>                 Key: WFLY-5043
>                 URL: https://issues.jboss.org/browse/WFLY-5043
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Web (Undertow)
>            Reporter: Michal Karm Babacek
>            Assignee: Stuart Douglas
>              Labels: mod_cluster
>
> As a follow up to JBEAP-215, this bug report is a member of a series addressing crucial CLI management capabilities.
> h3. Implement & Display node's Elected, Read, Transferred and Connected stats
> At the moment, this is all there is to see:
> {noformat}
> "balancer" => {
>     "qa_balancer" => {"node" => {"worker-2" => {
>         "load" => 89,
>         "status" => "NODE_UP",
>         "context" => {"/clusterbench" => {
>             "requests" => 0,
>             "status" => "enabled"
>         }}
>     }}},
> ...
> {noformat}
> Furthermore, at a glance, it appears that a part of the needed stats is a mere placeholder at the moment: [NodeStats.java|https://github.com/undertow-io/undertow/blob/master/core/src/main/java/io/undertow/server/handlers/proxy/mod_cluster/NodeStats.java]
> h3. Call to action
> Display the aforementioned stats for each node. Let me set priorities according to what is really used in the battlefield:
>  * {color:red}Critical{color}: *Elected* (it is often correlated with *Load* during load metric *history* and *capacity* tuning)
>  * {color:green}Minor{color}: *Read*
>  * {color:green}Minor{color}: *Transferred*
>  * {color:green}Minor{color}: *Connected*



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)