Terminal
Terminal/Skill
Checks whether an Azure Function App is running and healthy, using Resource Health, metrics, Application Insights and the Activity Log.
By Microsoft
Works with
npx skills add azure/azure-functions-skills --skill azure-functions-health-statusUse this skill to investigate the current status and health of an existing Azure Function App.
Write final answers in the user's language.
Ask only for missing inputs that are needed to identify the app and time window:
24h (optional)If subscription or resource group is unknown, discover them with Resource Graph. If multiple matching apps are found, ask the user to choose one.
azurefunctions first when available.scripts/get-functionapp-health-status.ps1 -AppName <app-name>scripts/get-functionapp-health-status.sh -a <app-name> on macOS/Linux or Bash-SubscriptionId <sub> and/or -ResourceGroup <rg> when known.-Hours <n> when the user requests a specific time window.-s <sub>, -g <resource-group>, and/or -H <hours> when known.python3 or python executable for JSON shaping.references/health-status-commands-and-kql.md.If health findings require runtime or trigger-specific interpretation, use ../azure-functions-common/references/routing.md on demand. Do not load shared language/extension references for plain status output.
This skill should collect:
Do not perform full static inventory beyond fields needed to interpret health. Use the inventory skill for detailed specifications.
azure-functions-diagnostics to interpret findings and recommend fixes when health signals are degraded or unclear.azure-functions-inventory to confirm app identity and configuration before retrying health checks.Unknown or Unsupported; rely on app metadata, plan status, metrics, telemetry, and Activity Log.AppRequests, AppExceptions, AppTraces, and AppDependencies; classic tables may be empty.%SETTING_NAME% placeholders in traces/exceptions as configuration/indexing issues.Target: <app> (<resource-group>, <subscription>, <region>)
Current status: app <state>, metadata <availability/runtime>, plan <status>, Resource Health <state/reason>
Metrics: instances <max/avg>, CPU <max>, memory <max>, executions <summary>
Execution: requests <n>, failed <n>, p95 highlights <...>; dependency failures <n>
Triggers: enabled <n>, disabled <n>; indexing/config issues <summary>
Recent changes: <Activity Log summary>
Findings: <1-3 bullets>
Recommended next actions: <1-3 bullets>
Gaps: <unavailable telemetry or unsupported checks>