John Crim

Note that https://github.com/Azure/azure-sdk-for-net/issues/45089 has some additional details on this. It was incorrectly closed (it has not been fixed, and will not be fixed by the consolidating issue) IMO.

@gboder - you can, but I would advise against switching to the OpenTelemetry exporter (if you're using the legacy one right now) unless you're game for doing a bunch of...

@ckschiefer - Exceptions become otel `LogRecord`s, and attributes on the `LogRecord`s become `customDimension`s. The Azure Otel exporter doesn't provide a way to override the mappings that it performs (which is...

Hi @TimothyMothra - thank you for the update. While I've been frustrated with some of the issues, you and your team have been responsive to the feedback, so I'm happy...

RE Tim's comment: > Unfortunately, I found some cases where the value in DisplayName was not sufficient so we won't be making any changes here. I don't think this PR...

Closing this since I don't think it's going anywhere. The fixes here should be handled by a fix for #46021

Note that [SCSS `@import` is deprecated in favor of `@use` and `@forward`](https://sass-lang.com/blog/import-is-deprecated/) and will be removed in the next major version; so while I like this idea I it should...

@carflynn2009 and @PeterEnevoldsen - this is the issue you brought up in #682. I came across the same issue today, so I investigated it and created a repro case.

@dragav - hope you don't mind me notifying you, since you've replied to SF MSI issues in the past, and SF issues don't seem to be getting triaged by anyone.

Thanks @amenarde - that's what I figured. Certainly the default should be WARN (since much of ASP.NET is still unhelpfully verbose at the INFO level), but it would be nice...