You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Making this attribute stable would allow making features that rely on it stable, relying on an experimental/incubating attribute transitively forces the feature as experimental/incubating.
Describe the solution you'd like
Making the code.stacktrace attribute stable, or making the whole code.* namespace stable.
Describe alternatives you've considered
Making the whole code.* attributes stable would be an alternative as most of those fields are not ambiguous even if some of their values are platform-specific (the code.stacktrace being a good example).
For now keeping the scope to code.stacktrace is a way to reduce the scope as an attempt to making this change easier.
Additional context
Making this attribute stable was discussed in August 29th Java SIG Meeting where the topic was "how to make a component in java contrib stable".
The text was updated successfully, but these errors were encountered:
OpenTelemetry contrib Java use code.stacktrace in inferred-spans and span-stacktrace modules as mentioned initially in the issue description.
In addition, as described in #1012 we know that the code.function, code.filepath and code.lineno have equivalent ECS (Elastic Common Schema), so while it does not count as direct usage, usages of those equivalent ECS fields can be mapped 1:1 to otel semconv.
When searching for text occurrences of those code.* attributes to see if there are other definitions I did not find anything that would contradict the current definitions, which means there is little ambiguity or things left to interpretation.
For example, I found similar references in:
Also, the value and format code.stacktrace is platform-specific and might be left to ambiguity or further specification, however it uses exactly the same definition of exception.stacktrace which is already stable.
Area(s)
area:code
Is your change request related to a problem? Please describe.
The
code.stacktrace
is currently experimental, and we think it would make sense to make it stable.Current known usages:
Making this attribute stable would allow making features that rely on it stable, relying on an experimental/incubating attribute transitively forces the feature as experimental/incubating.
Describe the solution you'd like
Making the
code.stacktrace
attribute stable, or making the wholecode.*
namespace stable.Describe alternatives you've considered
Making the whole
code.*
attributes stable would be an alternative as most of those fields are not ambiguous even if some of their values are platform-specific (thecode.stacktrace
being a good example).For now keeping the scope to
code.stacktrace
is a way to reduce the scope as an attempt to making this change easier.Additional context
Making this attribute stable was discussed in August 29th Java SIG Meeting where the topic was "how to make a component in java contrib stable".
The text was updated successfully, but these errors were encountered: