An Azure service that provides an event-driven serverless compute platform.
To check complete Azure Function logs for 12-Aug-2026, use the logs stored in Application Insights / Log Analytics instead of Log Stream. Log Stream is for live output, while historical function logs can be queried from the FunctionAppLogs table.
- In the Azure portal, open the Function App.
- Go to Diagnose and solve problems and run Function Configuration Checks.
- Verify that only one Application Insights setting exists:
-
APPLICATIONINSIGHTS_CONNECTION_STRINGor -
APPINSIGHTS_INSTRUMENTATIONKEY
-
-
APPLICATIONINSIGHTS_CONNECTION_STRINGis the recommended setting.
- Verify that only one Application Insights setting exists:
- If Application Insights is enabled, query the FunctionAppLogs table for the time window around the missing activity.
Example KQL to review logs around the reported time:
FunctionAppLogs
| where TimeGenerated between (datetime(2026-08-12 02:45:07.485) .. datetime(2026-08-12 02:49:07.488))
| project TimeGenerated, HostInstanceId, Level, Category, Message, FunctionInvocationId, FunctionName, ExceptionType, ExceptionMessage, _ResourceId
| sort by TimeGenerated asc
To focus on warnings and errors:
FunctionAppLogs
| where TimeGenerated between (datetime(2026-08-12 02:45:07.485) .. datetime(2026-08-12 02:49:07.488))
| where Level == "Warning" or Level == "Error"
| project TimeGenerated, HostInstanceId, Level, Message, ExceptionType, ExceptionMessage, FunctionInvocationId, FunctionName
| sort by TimeGenerated asc
To review execution results for function invocations:
FunctionAppLogs
| where TimeGenerated between (datetime(2026-08-12 02:45:07.485) .. datetime(2026-08-12 02:49:07.488))
| where Category startswith "Function." and Message startswith "Executed "
| parse Message with "Executed '" Name "' (" Result ", Id=" Id ", Duration=" Duration:long "ms)"
| project TimeGenerated, Name, Result, Id, Duration, FunctionInvocationId, _ResourceId
| sort by TimeGenerated asc
If logs stop after "Validation successful completion", check these areas:
- Sampling may be enabled and can limit telemetry sent to Application Insights.
- Log verbosity may be too low. Azure Functions logging can be controlled through
host.jsoncategories and log levels. - If the Function App is integrated with a virtual network, outbound port 443 must be open so telemetry can reach Application Insights endpoints.
- Use Diagnose and solve problems → Connectivity Troubleshooter to check outbound restrictions, DNS, storage, and firewall issues.
If diagnostic settings are configured, the Azure Functions-specific resource log is FunctionAppLogs.
Useful columns for this investigation are:
-
TimeGenerated -
Level -
Category -
Message -
FunctionInvocationId -
FunctionName -
ExceptionType -
ExceptionMessage -
HostInstanceId
- Application Insights logs are missing or incorrect for Azure Function App
- Application Insights logs are missing or incorrect for Azure Function App
- Queries for the FunctionAppLogs table
- Resolve "Function App Down or Reporting Errors" issues
- FunctionAppLogs
- Azure Functions monitoring data reference
- Viewing logs of Azure functions - Microsoft Q&A