Tagging subscribers to this area: @dotnet/area-extensions-logging
See info in area-owners.md if you want to be subscribed.

[LoggerMessage(EventId = 0, Level = LogLevel.Information, Message = "Excessively large timeout `{timeout}`")]
public static partial void ExcessivelyLargeTimeout(this ILogger logger, string timeout);
...
TimeSpan timeout = ...;
logger.ExcessivelyLargeTimeout(timeout.ToString());

CC @Youssef1313

Happy to implement once the analyzer is approved.

Analyzer would detect when "work" is being done in an argument call to an ILogger logging method. This basically boils down to anything other than a literal-expression, local-expression, parameter-expression, field-expression, property-expression, or indexer-expression (potentially recursively applied).

Note that this list includes identifying any parameters being wrapped in a new array to a params method call.

The analyzer should not fire if it identifies that it is in a scope that has already checked on log levels.

A logging method is any of:

• A method decorated with [LoggerMessage]
• Any of the extension methods on Microsoft.Extensions.Logging.LoggerExtensions
• A call to Microsoft.Extensions.Logging.ILogger.Log
• Anything else that looks like a logging method that we didn't think of today

Category: Performance
Severity: Suggestion

@buyaa-n I did a quick (not yet tested) prototype (dotnet/roslyn-analyzers#6643).

For now, I don't think I'll be able to complete it soon.

If anyone wants to pick it and continue on the code I wrote, this is totally fine.

Currently, the PR is missing:

• Tests

• The analyzer should not fire if it identifies that it is in a scope that has already checked on log levels.

• Fix any bad logic I could have wrote.

@Youssef1313 thanks for letting us know and having a draft PR we can use to build this analyzer.

I'd like to finish this analyzer :)

@mpidash thanks for willing to help with that. Please ensure doing it as described in #78402 (comment).