[
https://issues.apache.org/jira/browse/AMBARI-13310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943513#comment-14943513
]
Hudson commented on AMBARI-13310:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3596 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3596/])
AMBARI-13310. alerts should log into ambari-agent.log rather than to (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=33c8681709894495263ebc9f22f7825c08605155])
* ambari-common/src/main/python/resource_management/core/environment.py
* ambari-agent/src/main/python/ambari_agent/main.py
* ambari-agent/src/main/python/ambari_agent/alerts/script_alert.py
* ambari-agent/src/test/python/ambari_agent/TestMain.py
* ambari-agent/src/main/python/ambari_agent/AmbariConfig.py
> 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)
