You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Guangyuan Feng (Jira)" <ji...@apache.org> on 2023/06/07 04:22:00 UTC

[jira] [Assigned] (KYLIN-5560) To improving Kylin logging abilities

     [ https://issues.apache.org/jira/browse/KYLIN-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guangyuan Feng reassigned KYLIN-5560:
-------------------------------------

    Assignee: Yaguang Jia

> To improving Kylin logging abilities
> ------------------------------------
>
>                 Key: KYLIN-5560
>                 URL: https://issues.apache.org/jira/browse/KYLIN-5560
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Integration
>    Affects Versions: 5.0-alpha
>            Reporter: Guangyuan Feng
>            Assignee: Yaguang Jia
>            Priority: Major
>             Fix For: 5.0-alpha
>
>
> Currently most of the works, such as querying, are relying on the REST API, but Kylin lacks the measure to trace the whole life of a request, including accessing, handling, etc. Users have to pay much more time to find out the relations between the request and the corresponding procedures.
> In practice, we had add a new attribute `traceId` into each http request {*}HttpServletRequest{*}, and into *org.apache.kylin.rest.interceptor.KEFilter* utilizing log4j MDC(Mapped Diagnostic Context) tech to help us to improve the situation.
> So we hope our works could have the worth to improve Kylin.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)