Skip to content

Add a logline to include connection ID when describing a request and response pair - #88

Merged
Lincong merged 1 commit into
linkedin:2.3-li-1from
Lincong:add-logline-for-connection-id-1
Jun 18, 2020
Merged

Add a logline to include connection ID when describing a request and response pair#88
Lincong merged 1 commit into
linkedin:2.3-li-1from
Lincong:add-logline-for-connection-id-1

Conversation

@Lincong

@Lincong Lincong commented Jun 18, 2020

Copy link
Copy Markdown

The method Observer.describeRequestAndResponse is used to generate request/response information to log when the observer throws an exception. The generated request/response information will be logged together with the exception thrown by the observer.
Logging the connection ID along with the exception will help us understand how the value of connection ID plays a part in the exception and help us root cause the problem.

@gitlw

gitlw commented Jun 18, 2020

Copy link
Copy Markdown
  1. Please make sure you follow this format in the commit message, e.g.
    [LI-HOTFIX] Ignore the flaky test MetricsTest.testGeneralBrokerTopicMetricsAreGreedilyRegistered

TICKET = KAFKA-9786
LI_DESCRIPTION =
The test is flaky since gradle can use the same jvm to run multiple tests concurrently

EXIT_CRITERIA = KAFKA-9786

  1. Please also commit this change to the 2.4-li-dev-6 branch

…request and response pair

TICKET =
LI_DESCRIPTION =
The method Observer.describeRequestAndResponse is used to generate
request/response information to log when the observer throws an
exception. The generated request/response information will be logged
together with the exception thrown by the observer.
Logging the connection ID along with the exception will help us
understand how the value of connection ID plays a part in the exception
and help us root cause the problem.

EXIT_CRITERIA = Never since this is a linkedin internal change
@Lincong
Lincong force-pushed the add-logline-for-connection-id-1 branch from 5f263e5 to ac2e815 Compare June 18, 2020 17:22
@Lincong
Lincong merged commit e35a098 into linkedin:2.3-li-1 Jun 18, 2020
Lincong added a commit that referenced this pull request Jun 18, 2020
…request and response pair (#88)

TICKET =
LI_DESCRIPTION =
The method Observer.describeRequestAndResponse is used to generate
request/response information to log when the observer throws an
exception. The generated request/response information will be logged
together with the exception thrown by the observer.
Logging the connection ID along with the exception will help us
understand how the value of connection ID plays a part in the exception
and help us root cause the problem.

EXIT_CRITERIA = Never since this is a linkedin internal change
wyuka pushed a commit that referenced this pull request Jan 8, 2022
…request and response pair (#88)

TICKET =
LI_DESCRIPTION =
The method Observer.describeRequestAndResponse is used to generate
request/response information to log when the observer throws an
exception. The generated request/response information will be logged
together with the exception thrown by the observer.
Logging the connection ID along with the exception will help us
understand how the value of connection ID plays a part in the exception
and help us root cause the problem.

EXIT_CRITERIA = Never since this is a linkedin internal change
lmr3796 pushed a commit to lmr3796/kafka that referenced this pull request Feb 9, 2022
…request and response pair (linkedin#88)

TICKET =
LI_DESCRIPTION =
The method Observer.describeRequestAndResponse is used to generate
request/response information to log when the observer throws an
exception. The generated request/response information will be logged
together with the exception thrown by the observer.
Logging the connection ID along with the exception will help us
understand how the value of connection ID plays a part in the exception
and help us root cause the problem.

EXIT_CRITERIA = Never since this is a linkedin internal change
lmr3796 pushed a commit to lmr3796/kafka that referenced this pull request Mar 25, 2022
…request and response pair (linkedin#88)

TICKET =
LI_DESCRIPTION =
The method Observer.describeRequestAndResponse is used to generate
request/response information to log when the observer throws an
exception. The generated request/response information will be logged
together with the exception thrown by the observer.
Logging the connection ID along with the exception will help us
understand how the value of connection ID plays a part in the exception
and help us root cause the problem.

EXIT_CRITERIA = Never since this is a linkedin internal change
lmr3796 pushed a commit to lmr3796/kafka that referenced this pull request Jun 2, 2022
…request and response pair (linkedin#88)

TICKET =
LI_DESCRIPTION =
The method Observer.describeRequestAndResponse is used to generate
request/response information to log when the observer throws an
exception. The generated request/response information will be logged
together with the exception thrown by the observer.
Logging the connection ID along with the exception will help us
understand how the value of connection ID plays a part in the exception
and help us root cause the problem.

EXIT_CRITERIA = Never since this is a linkedin internal change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants