You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Doroszlai, Attila (JIRA)" <ji...@apache.org> on 2017/11/13 14:33:00 UTC
[jira] [Updated] (AMBARI-22426) Push down Logger instances
[ https://issues.apache.org/jira/browse/AMBARI-22426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doroszlai, Attila updated AMBARI-22426:
---------------------------------------
Attachment: AMBARI-22426.patch
> Push down Logger instances
> --------------------------
>
> Key: AMBARI-22426
> URL: https://issues.apache.org/jira/browse/AMBARI-22426
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 3.0.0
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-22426.patch
>
>
> {{Logger}} prepends classname and line number to log messages. Reusing {{Logger}} from other classes makes it more difficult to understand where the log message is coming from. This includes {{Logger}} instances inherited from parent classes.
> {noformat:title=example}
> 13 Nov 2017 11:55:13,571 INFO [ambari-client-thread-36] AbstractResourceProvider:525 - Creating Cluster 'TEST' based on blueprint 'blue'.
> 13 Nov 2017 11:55:13,623 ERROR [ambari-client-thread-36] BaseManagementHandler:79 - Caught a runtime exception while attempting to create a resource: null
> {noformat}
> In the above example, log is written from {{ClusterResourceProvider}} and {{CreateHandler}}, respectively, but one needs to search the source code for the messages to find this out.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)