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

Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2015/10/05 14:07:26 UTC

[jira] [Updated] (AMBARI-13310) alerts should log into ambari-agent.log rather than to ambari-agent.out

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

Andrew Onischuk updated AMBARI-13310:
-------------------------------------
    Description: The problem is that ambari-agent.out is not rolled and if ambari-agent is started for a long time, the out grows too huge. Also it's usefull to see alerts time in logs.

> alerts should log into ambari-agent.log rather than to ambari-agent.out
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-13310
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13310
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.2.0
>
>
> The problem is that ambari-agent.out is not rolled and if ambari-agent is started for a long time, the out grows too huge. Also it's usefull to see alerts time in logs.



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