A lot of redundant logs produced

[amaestr0]

Due to unresolved Kafka issue described here confluentinc/confluent-kafka-dotnet#1861
there are a lot of errors can be produced in log collection storage when the services run because of this error logging:

azure-functions-kafka-extension/src/Microsoft.Azure.WebJobs.Extensions.Kafka/Trigger/FunctionExecutorBase.cs

Line 91 in 59f93fb

this.logger.LogError(e, $"Commit error: {e.Error.Reason}");

Because the lib strangle errors within catch block - assuming the errors here aren't fatal/critical so the log level can be decreased.

So, can the log level be decreased or parametrized so lib consumer can control logs and decrease level on demand then a bunch of redundant logs could be omitted in logging system?

[jainharsh98]

We are working on upgrading the confluent kafka sdk to 2.4.0 - which seems to not have the above-mentioned Erroneous state issue. That should automatically take care of the unnecessary error logging for the extension.