Trask Stalnaker

ah, merge conflicts so the deploy preview is not rerunning 🤷‍♂️

@zeitlinger can you merge in `main` to fix the CI failures? thanks

> Would it make sense to use integer nanosecond timestamps to be consistent timestamp/duration measurement in the rest of [OpenTelemetry](https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/trace/v1/trace.proto#L191) hey @ladd 👋 I think this event is a bit...

> For the changelog, it will reuse and update the one from this PR #1940 it's better to create a change log entry (file) for each PR

thanks similar to https://github.com/open-telemetry/semantic-conventions/pull/1941#discussion_r2019321206, let's go ahead and land this browser-specific event initially, and explore generalizing it as follow-up work in the client instrumentation SIG we can deprecate the browser-specific...

I couldn't help noticing `k8s.resource_quota.*` spelled out with an `_` throughout this issue. Any chance you all changed your mind about naming these 😉? or is it just due to...

my initial thought is option 1 IIRC the purpose of making the port required when address is present was just to avoid the "default value" problem (does missing port imply...

I think it probably does require clarification, especially since that guidance would go against current spec "Conditionally Required if server.address is set." I've added this to Monday's semconv SIG agenda...

Discussed in SIG and consensus was that this is not a breaking change to relax this, since it does not affect metrics (`server.port` is opt-in on metrics) and previously instrumentation...

Action item from the maintainer SIG meeting is to come up with a name that will not be confused with OTel "common practices" from an end user perspective.