[ https://issues.apache.org/jira/browse/FINERACT-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksandar Vidakovic resolved FINERACT-1656. -------------------------------------------- Resolution: Fixed > Correlation ID propagation and configuration > -------------------------------------------- > > Key: FINERACT-1656 > URL: https://issues.apache.org/jira/browse/FINERACT-1656 > Project: Apache Fineract > Issue Type: Improvement > Reporter: Victor Romero > Assignee: Victor Romero > Priority: Major > Fix For: 1.8.0 > > > h2. Description > > The goal of this story is to provide a way for external systems to pass a > correlation ID as a request header to Fineract APIs so that a full trace of > request path can be looked at later on in a log aggregator > (Kibana/Splunk/etc). > *Acceptance criteria:* > * The correlation ID is taken from an HTTP request header > * The HTTP request header’s name is configurable via a Spring property and > an environment variable > * The default HTTP request header’s name is {{X-Correlation-ID}} > * If a correlation ID is provided, it’s inserted into the MDC context > * If a correlation ID is present in the MDC context, it’s included in the > log pattern > * The correlation ID propagation can be enabled and disabled via a Spring > property and an environment variable > *Note:* > The 2 properties could be called: > * {{fineract.logging.http.correlation-id.enabled=true/false}} > * {{fineract.logging.http.correlation-id.header-name=something}} > > > > > > > > > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)