Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Propagate log context data #288

Merged
merged 1 commit into from
Jul 19, 2016

Conversation

tfoel
Copy link

@tfoel tfoel commented Jul 1, 2016

Details of the Logging Contexts (MDC, ThreadContext, etc) are not sent to AI - this fix adds them as Custom Properties for each logging framework.

…t to AI - this fix adds them as Custom Properties for each logging framework.
@msftclas
Copy link

msftclas commented Jul 1, 2016

Hi @SFThomas, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@msftclas
Copy link

msftclas commented Jul 1, 2016

@SFThomas, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.

Thanks, MSBOT;

@Yonisha Yonisha merged commit 7aad07b into microsoft:master Jul 19, 2016
@sayhi2mukul
Copy link

Hi Yonisha,

Will this change be published as new version in maven repository.
http://mvnrepository.com/artifact/com.microsoft.azure/applicationinsights-logging-log4j2 shows 1.0.4 as latest version published in march.

Thanks,
Mukul

@OriYosefiMSFT
Copy link
Member

Hi Mukul,

We plan to release another version (including to Maven) soon. We do want to add a few more things first before we release the binaries though.

Thanks,
Ori

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.

5 participants