How can one get the log category when running Azure Functions locally?

I have a function app project where i have a mix of my code, some Azure storage interaction, some durable functions, entity framework, the whole soup. I want to be able to configure logs properly to hide irrelevant records. But the problem is that the default console logger doesn't output the Category of this or that log message so that I could add a corresponding filter in my host.json file. There is a possibility to add the "fileLoggingMode": "always" setting but that doesn't really help because it doesn't output the category either.

I assume one could simply deploy it to Azure and then grab the category from the AppInsights, but isn't there any locally available option which doesn't involve deployment?

Environment: .net7, function v4, dotnet-isolated.

UPD: just for clarity basically i wanna see a logger category for each of these log lines

Found the following possible solution. In the Program.cs:

            .ConfigureLogging(builder =>
            {
                builder.AddJsonConsole(options =>
                {
                    options.JsonWriterOptions = new JsonWriterOptions() { Indented = true };
                });
            })

and then in the console we'll have:

AFAIK,

There is a program called Azure Functions Core Tools installed in the local environment to run the Azure Functions. It shows in the console on every execution, what's happening such as executing the function, started logging, host lock release (Lease acquisition), etc. which may also known as Function Runtime Logs or Host Logs depends on the logs coming.

Default Host.json code:

{
    "version": "2.0",
    "logging": {
        "applicationInsights": {
            "samplingSettings": {
                "isEnabled": true,
                "excludedTypes": "Request"
            }
        }
    }
}

In order to avoid this type of information logs, you can set the log level in the host.json to:

 "logLevel": {
      "Function": "Error",
    }

Also, if those collective huge logs giving more cost, set the filters in the log level categories from the host.json code as I have shown in one of workarounds.