Use of "OTel native" or "native" referring to OpenTelemetry #3808
Replies: 10 comments 2 replies
-
cc @open-telemetry/docs-approvers I like this proposal, although I like to iterate over the exact terminology a little bit. What we want to express is "this library makes use of the OpenTelemetry API directly, there are no instrumentation libraries or any other workarounds needed". I also wonder if we need to make this specific to libraries, because right now we also have apps that use OpenTelemetry "natively". |
Beta Was this translation helpful? Give feedback.
-
A few additional suggestions:
|
Beta Was this translation helpful? Give feedback.
-
Btw, just a suggestion: we could host discussions under the Discussions section of this repo :). That would help keep discussion topics out of our already-busy Issues list. |
Beta Was this translation helpful? Give feedback.
-
There was some guidance in the otel community repo on when to use discussions and when not, let me double check on that, but overall I agree that we might use that instead of additional issues |
Beta Was this translation helpful? Give feedback.
-
TIL! I'll use Discussions from now on. |
Beta Was this translation helpful? Give feedback.
-
via https://github.com/open-telemetry/community/blob/main/docs/how-to-configure-new-repository.md:
|
Beta Was this translation helpful? Give feedback.
-
I would vote for otel-integrated. |
Beta Was this translation helpful? Give feedback.
-
@open-telemetry/docs-approvers please make suggestions what you prefer so we can get to a consensus :-) |
Beta Was this translation helpful? Give feedback.
-
Note, that "native instrumentation" is embedded in the spec:
|
Beta Was this translation helpful? Give feedback.
-
@svrnm Can we suggest a change upstream? Are we free to redefine or wrap that term in the docs? |
Beta Was this translation helpful? Give feedback.
-
We've around 230+ hits for "native" in our docs. It usually refers to native instrumentation, schemas, and so on.
I'd like to suggest that we come up with a new term and edit the docs accordingly. The term could be:
I think "native" might mean lots of things that are unrelated to technical aspects, so I'd rather go with "OTel-ready" or "OTel compatible", as boring as they might sound. That has the added benefit that one knows what the thing is native about.
+CC @svrnm
Beta Was this translation helpful? Give feedback.
All reactions