topic Mapped Diagnostic Context for Logging in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/mapped-diagnostic-context-for-logging/m-p/137387#M96312 <HTML><HEAD></HEAD><BODY><SPAN>We are deploying many mission critical applications. In case of an error, it is absolutely vital to have enough abundant amount of status information, so that operators could track the reason as soon as possible.</SPAN><BR /><SPAN>Even we need the log files to be read and analysed by a robot, so that the proper monitoring signal is fired. </SPAN><BR /><BR /><SPAN>But it is not a good idea to show so much information when they are not really needed. Mapped Diagnostic Context can be a good solution. by using MDC, developer sends more information to the logger. but what could be logged, can be configured by the operator.</SPAN><BR /><BR /><SPAN>More information could be found here:&nbsp;&nbsp; </SPAN><A href="http://logging.apache.org/log4j/2.x/manual/thread-context.html" rel="nofollow noopener noreferrer">http://logging.apache.org/log4j/2.x/manual/thread-context.html</A><SPAN> </SPAN><BR /><BR /><BR /><BR /><BR /><SPAN>Now these information are sent to the logger when available:</SPAN><BR /><SPAN>&nbsp;&nbsp; Process Definition ID</SPAN><BR /><SPAN>&nbsp;&nbsp; Process execution Id</SPAN><BR /><SPAN>&nbsp;&nbsp; Business Key</SPAN><BR /><SPAN>&nbsp;&nbsp; Task Id</SPAN><BR /><BR /><SPAN>the user can configure the output to show the above information as he needs. Something like:</SPAN><BR /><SPAN>&nbsp;&nbsp; log4j.appender.FILE.layout.ConversionPattern=&nbsp;&nbsp; %X{mdcProcessExecutionID}&nbsp; %d{yyyy-MM-dd}-%t-%x-%-5p-%-10c:%m%n</SPAN><BR /><BR /><BR /><SPAN>I have created a sample implementation, to share with others, if this is the best way to do it.</SPAN><BR /><SPAN>And also a jira issue, to track the changes</SPAN><BR /></BODY></HTML> Fri, 05 Jul 2013 14:01:29 GMT smirzai 2013-07-05T14:01:29Z Mapped Diagnostic Context for Logging https://connect.hyland.com/t5/alfresco-archive/mapped-diagnostic-context-for-logging/m-p/137387#M96312 We are deploying many mission critical applications. In case of an error, it is absolutely vital to have enough abundant amount of status information, so that operators could track the reason as soon as possible.Even we need the log files to be read and analysed by a robot, so that the proper monito Fri, 05 Jul 2013 14:01:29 GMT https://connect.hyland.com/t5/alfresco-archive/mapped-diagnostic-context-for-logging/m-p/137387#M96312 smirzai 2013-07-05T14:01:29Z Re: Mapped Diagnostic Context for Logging https://connect.hyland.com/t5/alfresco-archive/mapped-diagnostic-context-for-logging/m-p/137388#M96313 <HTML><HEAD></HEAD><BODY><SPAN>Here is the related Jira Issue: </SPAN><A href="http://jira.codehaus.org/browse/ACT-1738" rel="nofollow noopener noreferrer">http://jira.codehaus.org/browse/ACT-1738</A></BODY></HTML> Fri, 05 Jul 2013 14:13:17 GMT https://connect.hyland.com/t5/alfresco-archive/mapped-diagnostic-context-for-logging/m-p/137388#M96313 smirzai 2013-07-05T14:13:17Z