Carlos Alberto Cortez

I saw 1.14 was just released - so it means one more month to go with the out of date metrics, right? (And yes, the docs should be autogenerated -...

Hey @anuraaga! Yes, local testing - no, sadly I don't run an IDE ;) But your comment makes me believe no build refactoring/extension is needed, and probably I can dig...

Thanks @dehaansa - I think there's value in defining them anyway, as we will need them one way or another. Also, it may to your interest specifically that I'd like...

@dehaansa You maybe interested in the latest iterations in https://github.com/open-telemetry/opentelemetry-specification/pull/2485 - so far: * Most gauges have become UpDownCounters * Have left out of the semantic conventions a few metrics...

@rochdev Hey, sorry for the late answer. Agreed with what you wrote - but what names you think we should use? @tylerbenson already mentioned `direct`/`indirect` as options, and if you...

After giving this a try via #906, we decided to postpone it in order to develop it properly. Re-labeling it so we can add this feature after GA.

> In some cases the more generic conventions will be actually sufficient to express what the more specific convention aims to capture. Yes, unfortunately writing generic semantic conventions may be...

@djaglowski I like your proposal as a starting point. One thing I'd like to see is that OTel components (receivers, instrumentation) include a very short but clear document with the...

+1 on making this `release:after-ga` .

@bogdandrutu Any opinion on https://github.com/open-telemetry/opentelemetry-proto/issues/400#issuecomment-1161848977 ?