[erlang-questions] seq_trace with bigint labels

Tristan Sloughter t@REDACTED
Wed Jan 24 17:26:43 CET 2018

Great! And yea, it doesn't have to be dynamic. For census it needs to be
128bits for the trace id and span ids are 64bits.
  Tristan Sloughter
  "I am not a crackpot" - Abe Simpson

On Wed, Jan 24, 2018, at 1:34 AM, Kenneth Lundin wrote:
> I will take it up to discussion within the OTP team and come back with
> an answer as soon as possible.> The idea with the small_int solution is that we wanted an immediate
> data here to avoid dynamic memory allocation. But I think it would be
> possible to allow a bigger> value which still is of fixed size (big int is dynamic).
> I think it would be very good if seqtrace could support use cases
> like this.> 
> /Kenneth, Erlang/OTP team at Ericsson
> On Tue, Jan 23, 2018 at 6:12 PM, Tristan Sloughter
> <t@REDACTED> wrote:>> > Ideally we'd have a solution where the individual applications
>> > would not>>  > have to be modified/recompiled but the whole node could be
>>  > configured to>>  > send trace data out to a trace collector.
>>  Mostly. You'd still need to include the app that is capable of
>>  receiving the seq_trace messages and formatting spans to be reported
>>  from them, but you'd be able to trace any message path without code
>>  modifications.>> 
>>  But yea, I don't know either if it is as simple as letting it use
>>  bigints, or what the consequences of doing so would be.>> 
>>  Hopefully someone on the OTP team sees this and can answer :)
>> _______________________________________________
>>  erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180124/a9a982fb/attachment.htm>

More information about the erlang-questions mailing list