[
https://issues.apache.org/jira/browse/FINERACT-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469361#comment-17469361
]
Michael Vorburger commented on FINERACT-999:
--------------------------------------------
FINERACT-892 probably would naturally include this kind of thing (as additional
custom "tagged label fields").
> Include git revision in (each) log statement
> --------------------------------------------
>
> Key: FINERACT-999
> URL: https://issues.apache.org/jira/browse/FINERACT-999
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Michael Vorburger
> Priority: Major
>
> During FINERACT-932, it occurred to me that it could be useful, when
> analysing error logs, to know in exactly which git revision an error log was
> produced, e.g. because line numbers may have changed in the mean time etc.
> https://github.com/spring-projects/spring-boot/issues/11950 has something
> about including it in the Spring Boot banner - but that is easily lost in a
> long running application, and not immediately visible e.g. in
> https://cloud.google.com/error-reporting.
> What would be nicer is if each log statement, literally every line, would
> simply include the Git revision. This should be possible through a custom log
> format acessing something from a global context (not MDC), somehow.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
