Azure Functions Integration
Observe serverless function executions, bindings, and cold start metrics on Azure. Get predictive alerts and AI anomaly detection before function failures impact your users.
How It Works
Register a Service Principal
Create an Azure Service Principal with the Monitoring Reader role on your Function App resource group. TigerOps uses this to poll Azure Monitor metrics and Application Insights telemetry.
Enable Application Insights
Link your Function App to an Application Insights workspace. TigerOps reads execution counts, failure rates, and dependency call durations directly from the AI telemetry pipeline.
Configure Diagnostic Settings
Route Function App platform logs and metrics to a Log Analytics workspace. TigerOps ingests cold start durations, throttle events, and binding error rates from these streams.
Set Execution Thresholds
Define SLOs for cold start p99, execution duration, and failure rate per function. TigerOps alerts before SLOs are breached and correlates cold starts with plan scaling events.
What You Get Out of the Box
Cold Start Latency Tracking
Per-function cold start duration percentiles (p50, p95, p99) with correlation to hosting plan type, runtime version, and deployment size. Identify which functions benefit from Premium plan pre-warming.
Execution Success & Failure Rates
Invocation counts, success rates, and exception class breakdown per function and trigger type. Drill from aggregate failure rate to individual exception stack traces instantly.
Binding Health Monitoring
Track trigger queue depths, blob storage binding latency, and Service Bus binding throttle events. Detect binding-level bottlenecks before they cause function timeouts.
Concurrency & Throttling Insights
Active instance counts, concurrent execution limits, and HTTP 429 throttle rates across Consumption and Premium plans. See exactly when your plan capacity is exhausted.
Dependency Call Performance
Outbound HTTP, SQL, and storage dependency call durations and failure rates traced from within function executions. Identify slow downstream services causing function timeouts.
AI Anomaly Detection
TigerOps AI learns your function execution baselines and flags unusual cold start spikes, failure rate deviations, or sudden concurrency drops with contextual root cause suggestions.
Azure CLI — Link Function App to TigerOps
Enable Application Insights and Diagnostic Settings for your Function App in minutes.
#!/bin/bash
# TigerOps — Azure Functions integration setup
RESOURCE_GROUP="my-resource-group"
FUNCTION_APP="my-function-app"
WORKSPACE_ID="/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.OperationalInsights/workspaces/tigerops-workspace"
# 1. Create Service Principal with Monitoring Reader
az ad sp create-for-rbac \
--name tigerops-functions-reader \
--role "Monitoring Reader" \
--scopes "/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}"
# 2. Enable Application Insights on the Function App
az monitor app-insights component create \
--app tigerops-insights \
--location eastus \
--resource-group "${RESOURCE_GROUP}" \
--workspace "${WORKSPACE_ID}"
az functionapp config appsettings set \
--name "${FUNCTION_APP}" \
--resource-group "${RESOURCE_GROUP}" \
--settings APPINSIGHTS_INSTRUMENTATIONKEY="${INSTRUMENTATION_KEY}"
# 3. Enable Diagnostic Settings
az monitor diagnostic-settings create \
--name tigerops-diagnostics \
--resource "/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.Web/sites/${FUNCTION_APP}" \
--workspace "${WORKSPACE_ID}" \
--metrics '[{"category":"AllMetrics","enabled":true}]' \
--logs '[{"category":"FunctionAppLogs","enabled":true}]'
# 4. Add TigerOps API key to Function App settings
az functionapp config appsettings set \
--name "${FUNCTION_APP}" \
--resource-group "${RESOURCE_GROUP}" \
--settings TIGEROPS_API_KEY="${TIGEROPS_API_KEY}"Common Questions
Does TigerOps support all Azure Functions hosting plans?
Yes. TigerOps monitors Consumption, Premium, and Dedicated (App Service) plan functions. Cold start metrics are most relevant for Consumption plan functions and TigerOps labels them accordingly in dashboards.
How does TigerOps collect cold start data?
Cold start durations are extracted from Application Insights dependency telemetry and the FunctionExecutionDuration metric in Azure Monitor. TigerOps distinguishes cold starts from warm invocations using the host instance identifier.
Can I monitor Durable Functions with TigerOps?
Yes. TigerOps tracks Durable Function orchestrator and activity execution counts, pending activity queue depths, and sub-orchestration failure rates through the Azure Storage trigger metrics emitted by the Durable Task Framework.
What runtimes are supported?
TigerOps supports all Azure Functions runtimes — .NET, Node.js, Python, Java, and PowerShell — across Functions runtime v3 and v4. Metrics are runtime-agnostic as they are collected at the platform level.
How are Azure Functions alerts correlated with other services?
TigerOps links function execution failures to downstream dependency health, upstream event trigger queue depth, and any infrastructure changes (deployments, plan scaling) that occurred in the same time window.
Stop Debugging Cold Starts in the Dark
Execution metrics, cold start latency, and AI anomaly detection for Azure Functions. Deploy in 5 minutes.