Dhaval Doshi

@reyang @littleaj could you please help reviewing this contribution. In short, it is to improve our exception capturing ability by triming down the stack trace size to what is supported...

@vlev a quick comment on naming first. I would rather prefer something different than traceLength. trace is common terminology in Distributed Tracing (a.k.a correlation) and also is sometimes intermixed as...

@vlev to give you some more context, we need to think a bit about this design overall. It might be a good idea to have these properties configurable, however it...

> Also, this configuration might be useful for those who want to apply some constrains on the amount of data being sent and stored in AI backend. Regarding this, yes...

@SergeyKanzhelev do we face similar issue in .NET SDK? If yes, how did we resolved that? If not, what are your thoughts on above approach from @vlev

@trask FYI - this issue persist in our SDK ( where huge stack traces are not sent due to schema limits). This is a design question in general and @reyang...

@bputt yes, you are correct. "Provide decorator based support" is essentially # 1 for less popular clients. I would imagine something like Reactor (not less popular per say, but hard...

> I'd like to suggest this supporting > > 1. Automatic injection of X-B3 headers > 2. Automatic injection of a set of headers w/ values (For example, if we...

@bputt in order for the wole tracing to work other libraries would also have to adopt a similar approach of interoping different headers, but in my perspective it would be...

@bputt agreed, but it would not be 100% the case that downstream libraries would support W3C (we can hope so). So just to clarify my previous comment: OC -> Have...