[
https://issues.apache.org/jira/browse/AMBARI-16734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitiraj Singh Rathore updated AMBARI-16734:
-------------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk and branch-2.4 by [~pallavkul]
> View log files should pickup ambari-server log directory path
> -------------------------------------------------------------
>
> Key: AMBARI-16734
> URL: https://issues.apache.org/jira/browse/AMBARI-16734
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.2.2
> Reporter: Nitiraj Singh Rathore
> Assignee: Nitiraj Singh Rathore
> Fix For: 2.4.0
>
> Attachments: AMBARI-16734_branch-2.4.patch
>
>
> Right now, each view hard-codes their path:
> log4j.appender.tezView.File=/var/log/ambari-server/tez-view/tez-view.log
> But with Ambari Server log, the user can change the /var/log/ambari-server in
> /etc/ambari-server/conf/log4j.properties.
> # Define some default values that can be overridden by system properties
> # Root logger option
> ambari.root.dir=/
> ambari.log.dir=${ambari.root.dir}/var/log/ambari-server
> ambari.log.file=ambari-server.log
> So the view logs need to inherit ambari.log.dir vs. hardcoding
> /var/log/ambari-server
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
