You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@falcon.apache.org by "Ajay Yadava (JIRA)" <ji...@apache.org> on 2015/09/27 09:25:05 UTC

[jira] [Updated] (FALCON-1475) Separate SLA monitoring logs from application logs

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

Ajay Yadava updated FALCON-1475:
--------------------------------
    Fix Version/s: 0.8

> Separate SLA monitoring logs from application logs
> --------------------------------------------------
>
>                 Key: FALCON-1475
>                 URL: https://issues.apache.org/jira/browse/FALCON-1475
>             Project: Falcon
>          Issue Type: Sub-task
>         Environment: QA
>            Reporter: Pragya Mittal
>            Assignee: Ajay Yadava
>             Fix For: 0.8
>
>
> Currently SLA Monitoring runs as service. Hence it keeps on monitoring entities until the path is not there. These should be separated form current application logs so that user can have a clear idea with respect to SLA behaviour and its breach. 



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