John Watson

The only thing you want to configure is the time unit? Not the interval itself?

> Hi [@jkwatson](https://github.com/jkwatson) [@gabgg71](https://github.com/gabgg71), I'm picking up this issue from Ellen. It seems like it makes the most sense to be able to configure both the interval and the time...

> [@jack-berg](https://github.com/jack-berg) I spoke with my team and we discussed an easier solution for our [related issue](https://github.com/OpenLiberty/open-liberty/issues/30642); perhaps if it's not preferable to expose the configuration values for the ThrottlingLogger...

yeah, the command line resource attribute is very often problematic. I wonder if this is something we should consider removing by default, @jack-berg @trask

I don't understand what that spec reference is trying to say, TBH. Are we missing a part of the shim implementation that we should have?

Yes, I read all of that before. I don't know what you're proposing as a solution, though, and the spec reference doesn't seem to clarify anything for me. Is our...

Are you trying to use io.opentelemetry.exporter.internal.http.HttpExporter with a custom sender? If you have a fully custom exporter implementation, you should never run into any code in HttpExporter, which is internal...

> > Are you trying to use io.opentelemetry.exporter.internal.http.HttpExporter with a custom sender? If you have a fully custom exporter implementation, you should never run into any code in HttpExporter, which...

I don't think the as-of-yet-incomplete "event" API will support severities, or bodies. Just names and attributes, like our span events do.

> Once we have a stable Event API and data model, I recommend that we deprecate the SpanEvents API. This will alleviate confusion. Instead of trying to explain why you...