Santosh Cheler
Santosh Cheler
@jsuereth @reyang @bogdandrutu @tigrannajaryan can we have a TC member assigned to this project? We are stuck again with https://github.com/open-telemetry/opentelemetry-js/issues/3222 which needs a future-proof path to [Ephemeral Resource Attributes[(https://github.com/open-telemetry/oteps/pull/208) -...
@jsuereth We can definitely change the SIG meeting time to accommodate a TC member's schedule. The core members of this SIG (myself, @martinkuba and @MSNev) meet on Tuesdays 9am PT...
To me this sounds like a topic of semantic conventions for instrumenting build pipelines. See the following sample payload (the timestamps are not adjusted) - we can model the build...
@abitrolly the reason for using spans would be to leverage the tooling built for spans by the telemetry backends (visualization, analytics, correlation, etc). Otherwise, I agree that everything can be...
@dyladan can you please clarify what you meant by `we use scope for the OTLP`? We still see `instrumentationLibrary` in the OTLP exported by the browser.
@dyladan never mind, we were using an older version of otlp exporter.
@jpkrohling Client Instrumentation SIG would be a good place to take this forward. We discussed this topic in the Client SIG with @johnbley a few weeks ago and we realized...
@jsuereth any update on having a TC member help us on this project? Did you get a chance to raise it in a TC meeting?
@jpkrohling @johnbley The current `traceresponse` spec only enables the client to add a span link to the server side span, it does not enable the typical parent-child relationship of spans...