An Azure service that provides an event-driven serverless compute platform.
Hi @Kim Strasser ,
Thanks for the offline conversation. Glad the issue is resolved.
The setting:
AzureFunctionsJobHost__logging__logLevel__default=Warning
is an environment variable used by Azure Functions to control the default log level for the Functions host.
If you have a host.json setting for logLevel.default, this environment variable takes precedence in Azure App Settings.
Setting it to Warning helps reduce unnecessary Information or Debug logs, which can:
- Lower Application Insights costs
- Reduce noise in production logs
You can check couple of places in the Portal where you can watch the logs:
- Log streaming (“live” console output)
- In the Azure Portal, navigate to your Function App
- In the left-hand menu under Monitoring, click Log stream
- You’ll see the real-time output (Information, Warning, Error) from your functions as they execute
- Application Insights
- Make sure you’ve turned on Application Insights for your Function App (via the Instrumentation Key or Connection String in Configuration =>Application settings)
- Open the linked Application Insights resource, go to Logs, and run a query over the
traces(orexceptions) table to see past invocations and log levels - You can also use Live Metrics Stream for a near-real-time view of incoming telemetry
- Monitor blade (invocation summary)
- In your Function App, click Monitor in the left menu to see a history of executions, durations, success/failures and link into Application Insights if enabled.
Note: if you're stepping through code locally in Visual Studio, those Debug.Write/ILogger outputs appear in your local console window, not in the Portal. You'll need to publish/deploy (or attach an Application Insights SDK locally) for the Portal blades above to pick them up.
Hope that helps!