Closed milenkovicm closed 6 years ago
Hi @ivantopo could you please have a look if this is something you'd merge to master?
Hey @milenkovicm! I'm a bit tied up until end of day, will check it out then :)
Hi @ivantopo I'm not sure that I understand part of the comment about
There is one additional thing that this should have, which is making sure that this behavior can be disabled and other keys could be added to the MDC
can you give some more clarifications, not sure which other keys you're referring to.
Hi @ivantopo, updated according to your comments, please have a look whenever you have time.
hey @milenkovicm!
There is one additional thing that this should have, which is making sure that this behavior can be disabled and other keys could be added to the MDC
By that I meant two things:
Since item 1 is already implemented and the actual reason for this PR I think we can merge it and work on the second item afterwards. What do you think?
Thanks for your comment @ivantopo, My main motivation for this PR was to be able to correlate traces with logs, for that use traceid is sufficient. But I also see value of having other keys there.
Please merge this one, we can add additional keys later
Hey @milenkovicm! man, sorry, I forgot to ask you to electronically sign the CLA, please sign it and we will merge this, thanks!
done
thanks a lot @milenkovicm! :tada:
thank you! let me know when you release it so i can update deps
Hi guys,
I'd like to put
traceID
andspanID
in MDC map as some libraries (e.g logstash/logstash-logback-encoder) will encode all data available in MDC without any additional configuration.