Yuri Shkuro
Yuri Shkuro
Not claiming it's a best practice, but just as a reference to what we did in Jaeger. Website footer contains a link to report security issues  which takes you...
I would also recommend each repo to add an issue template "Report a security vulnerability". Cf: https://github.com/jaegertracing/jaeger/issues/new/choose
@tedsuo the Jaeger project has often participated in Outreachy, which provides internships to minorities. However, the nature of internships is such that people finish them and move on to something...
NB: it's fine to point to OTEL.io site if it's going to have the same documentation, it's better to keep a single copy. With OpenTracing we usually kept the website...
Agree with @anuraaga, if a more descriptive name is available, why is the span name set to `HTTP `, which is only meant for the worst case? The change itself...
Copying from https://github.com/open-telemetry/opentelemetry-specification/issues/1971#issuecomment-928179220 It was added to Jaeger (https://github.com/jaegertracing/jaeger/issues/755#issuecomment-393929718), apparently because Brave/Sleuth already used `baggage-***` format, although their authors were not especially happy with it (https://github.com/openzipkin/b3-propagation/issues/22#issuecomment-391902496). Looking at [Brave docs][1],...
+1, especially if dependent-on could be checked by a function. We have a bunch of flags like `*.tls.*`, which only make sense when `*.tls.enabled=true`. When `*.tls.enabled` is omitted, it defaults...
Accepting JSON config does not provide more backwards compatibility guarantees than accepting a config struct. Passing string configs like this is pretty weird, I would recommend code-first API, and if...
Would you like to submit a PR? Besides the logic fix it would need to add v8 to the CI steps.
@Ashmita152 I came across https://github.com/olivere/elastic/issues/1533, where the author of the library unequivocally states: > Elastic v8 won't happen. I will polish v7 if I have the time and energy, but...