Jack Berg

> It's my current understanding that if buzz is not added to the configuration file, it should not be enabled. But perhaps that's my misunderstanding of how this is supposed...

> Maybe these additional preset lists are better managed through configuration examples Yes, my opinion is that this should be communicated via examples or using higher order templating tools like...

For reference, the version of `opentelemetry-proto` we work off of is defined here: https://github.com/open-telemetry/opentelemetry-java/blob/main/dependencyManagement/build.gradle.kts#L75 Should find a way to allow this version to be highlighted in the [README](https://github.com/open-telemetry/opentelemetry-java/blob/main/README.md) and possibly...

Yes, the line number is subject to change, but here's a permalink to the version in the latest commit in `main` as of 3/4: https://github.com/open-telemetry/opentelemetry-java/blob/0a993b392c8696d09922615938a8e05c50cc5ed6/dependencyManagement/build.gradle.kts#L88

> Ideally I'd like to have some control over how that attribute ends up being rendered and to avoid the default rendering. What do folks (including @open-telemetry/java-approvers) think about adding...

On the other hand, I can't find a way to actually produce a truncated stack trace besides vendoring in the logic from `Throwable#printStackTrace()`, so not how useful it would be...

If I recall correctly, the context for this issue was about lambda instrumentation. There was disagreement over a PR that was merged to semantic conventions and the lambda maintainers declined...

Relevant discussion here as well: https://github.com/open-telemetry/opentelemetry-configuration/issues/334#issuecomment-3488232714

I agree. Sounds like we have a plan.

@breedx-splk given `opentelemetry-android`'s usage of the event API / SDK, I'm interested in what you think about this.