Nev

I would 2nd what @trask is suggesting, this looks like it would map to the severity which is already available as an optional field (as not all events want /...

@thompson-tomo Not all events will represent "success percentage &/or a counter of success/failure events" scenarios. So as I called out above, there is nothing stopping these specific events from providing...

Not at this point, once we have scheduled the work we normally create and assign a milestone to it.

> Application Insights is logging the 404 error to the console I don't believe that we are the source of logging to the console?? At least by default we should...

That doesn't look like one of our error messages from the SDK, doing a quick search online this error message might be associated with the page not being able to...

https://github.com/open-telemetry/semantic-conventions/issues/1230

I'm a little concerned that by "defining" the way that "enabled" should be implemented (especially adding layers of filtering (as part of the required implementation)) would (potentially) worse from a...

I think it's fine to define "what" options should be used (ie the parameters) to "check" whether something is enabled or not and this should be limited. If an end-user...

> I am not sure if I follow. > > `Logger.Enabled` gives the possibility to for the user to check if it is even necessary to construct and emit a...

I create a draft for this last week, but I've had is closed so that we could discuss in the SIG meeting today -- I've just reopened it https://github.com/open-telemetry/opentelemetry-specification/pull/4252 --...