You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/10/14 12:10:05 UTC

[jira] [Updated] (SLIDER-945) build up history of request/release/failures for each component and serve in the REST API (and web UI?)

     [ https://issues.apache.org/jira/browse/SLIDER-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated SLIDER-945:
----------------------------------
    Issue Type: Sub-task  (was: New Feature)
        Parent: SLIDER-82

> build up history of request/release/failures for each component and serve in the REST API (and web UI?)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: SLIDER-945
>                 URL: https://issues.apache.org/jira/browse/SLIDER-945
>             Project: Slider
>          Issue Type: Sub-task
>          Components: appmaster, Web & REST
>    Affects Versions: Slider 0.80
>            Reporter: Steve Loughran
>             Fix For: Slider 0.90
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> For testing things like SLIDER-82, it'd be good to have a history where we can list events for each component (e.g. requested containers, released containers, failed container, escalation). This would be a structured log which could be viewed in the REST API for each component, and parseable for the test runner to get a view of what happened to get the cluster to its current state;
> Could be good as an HTML view too, so you can see what's going on. We do end up looking in the AM logs for this kind of information, after all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)