falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadava (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FALCON-1475) Separate SLA monitoring logs from application logs
Date Sun, 27 Sep 2015 07:25:04 GMT

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

Ajay Yadava resolved FALCON-1475.
    Resolution: Fixed

Fixed as part of FALCON-1472

> 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
> 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

View raw message