Alberto Sartori
Alberto Sartori
Ops, yes sure, I may have missed a couple of "save without formatting"... don't know why the editor is not honouring my settings
Reverted the format changes
@tsloughter sorry, busy days, I'll go through comments later today or tomorrow
> So I'm less sure of this now. We shouldn't need to be storing all the attribute information like limits on each datapoint, right? > > Plus this would mean...
The only ways I can think of are: * duplicating the implementation of the feature on Elixir side * somehow add a metadata when using the Elixir version of `with_span`...
The problem is that in both these cases ```erlang %% ERROR ?assertException(error, badarg, otel_tracer:with_span(Tracer, , #{record_exception => true}, fun(_SpanCtx) -> erlang:error(badarg) end)), receive {span, SpanError} -> ?assertEqual(, SpanError#span.name), ?assertEqual(undefined, SpanError#span.status),...
There is something similar also in Elixir core, where Erlang exception are translated to Elixir ones. This is exactly what is causing problems here: the logic for recording the exception...
I may have found a solution. I take the first element of the stacktrace and use it to know if the exception was raised from Erlang or Elixir so that...
> I'm very interested in use case 5, since we already have our own web server and do not want to export an additional port. Yea, I think this will...
@tsloughter I'll try this weekend hoping things have not changed too much. Unfortunately in the last months I was not able to follow the project with constancy