You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org> on 2013/10/11 07:42:47 UTC

[jira] [Commented] (FALCON-37) Falcon - Dashboard Feature

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

Srikanth Sundarrajan commented on FALCON-37:
--------------------------------------------

As further refinement to the proposal, my suggestion would be to do the following

* Dashboard opens up with a time slider (defaults to last few hours) and a search bar
* Search bar can accept entity names (feed, process, cluster, datasource etc...), feed group tags, process pipeline tags (FALCON-48) or tags (FALCON-29) (ConfigStore::search to be leveraged for this)
* Retrieve and render entities that match the search criteria with upto 2 levels of depth in dependencies (Entity Graph to be leveraged for this)
* Indicate the health of each of the entities based on the instance status within the time range selected through the slider (Instance state db to power this)
* Instance status are to be tracked based on information that falcon can start recording in a db (Instance state db). Source of this data would be the post-processing-message that falcon subscribes to.
* Through the dashboard it should be possible to monitor health collectively over a time period and individual feed availability & process execution status, besides having the ability to look at historical trends

Thoughts?

> Falcon - Dashboard Feature
> --------------------------
>
>                 Key: FALCON-37
>                 URL: https://issues.apache.org/jira/browse/FALCON-37
>             Project: Falcon
>          Issue Type: New Feature
>          Components: general
>    Affects Versions: 0.4
>            Reporter: Srikanth Sundarrajan
>            Assignee: Srikanth Vittal
>         Attachments: Falcon – Dashboard.pdf
>
>




--
This message was sent by Atlassian JIRA
(v6.1#6144)