Carlos Alberto Cortez
Carlos Alberto Cortez
The OT Shim layer needs to be updated to include the latest changes as introduced by https://github.com/open-telemetry/opentelemetry-specification/pull/1101 https://github.com/open-telemetry/opentelemetry-specification/pull/1563
There you go, and notes on the impl: - Could not show more chaining actual promises, as we don't support that yet (may take a look after the release) -...
Lemme know ;)
It looks like SpiderMonkey, in the case of sparse arrays, fallbacks to simple property access\* (i.e. arr[450] gets the '450' property, if any). Wouldn't that work here for now, instead...
There have been discussions regarding maintaining/shipping instrumentation from repos outside the main OpenTelemetry organization, given that: - There are only so many maintainers/approvers, which may result in constant bottlenecks regarding...
The OT Shim layer needs to be updated to include the latest changes as introduced by https://github.com/open-telemetry/opentelemetry-specification/pull/1101 https://github.com/open-telemetry/opentelemetry-specification/pull/1563
My impression is that most users of OT use it in manual fashion, i.e. no automatic instrumentation. But we should do a double check in case there's value in putting...
Initial pass for a few semantic convention updates: * Loaded classes. * Unloaded classes. * Active threads. Will update the rest in a second pass: * Still to be decided...
PR with the upcoming changes from https://github.com/open-telemetry/opentelemetry-specification/pull/2485 - observe not all metrics are included, namely: * Metrics which could use Summary points instead (changes have been postponed) * Consumer metrics...