Azure Logic Apps Integration
Workflow run metrics, action success rates, and trigger execution counts for Azure Logic Apps. Detect failing automation workflows and slow business processes before they escalate.
How It Works
Assign Monitoring Reader
Grant the TigerOps Service Principal the Monitoring Reader role on your Logic Apps resource group. TigerOps collects workflow run, action, and trigger metrics from Azure Monitor without needing Logic App edit permissions.
Enable Diagnostic Settings
Turn on Diagnostic Settings for each Logic App to stream WorkflowRuntime logs and AllMetrics to a Log Analytics workspace. This provides per-action execution detail.
Map Critical Workflows
Tag your critical Logic Apps workflows in TigerOps with business process labels. The integration groups run metrics by workflow and exposes SLO compliance dashboards per business process.
Set Run Failure Alerts
Configure failure rate thresholds per workflow. TigerOps fires alerts when run failures exceed your threshold and includes the failed action name and error message for fast triage.
What You Get Out of the Box
Workflow Run Tracking
Total runs, succeeded, failed, and skipped run counts per Logic App with run duration percentiles. Track SLO compliance for business-critical automation workflows.
Action Success Rate Monitoring
Per-action execution counts, success rates, and failure reasons within each workflow run. Identify which connector actions fail most often and drill into the specific error codes.
Trigger Execution Counts
HTTP trigger request rates, recurrence trigger fire counts, and event-based trigger activation frequency. Monitor trigger health and detect triggers that stop firing due to upstream failures.
Run Duration Analysis
Workflow run duration at p50, p95, and p99 with historical trending. Detect when a Logic App workflow is taking significantly longer than its baseline and trace the slowest actions.
Throttling & Billing Units
Throttled action counts, billing meter units consumed, and connector call quotas. Understand your Logic Apps consumption costs and plan capacity before throttle limits are hit.
AI Workflow Anomaly Detection
TigerOps AI learns normal run frequency and duration baselines per workflow. Unusual run volume spikes, sudden failure rate increases, or extended run durations are flagged with context.
Enable Logic Apps Diagnostics
Stream workflow runtime logs and metrics to Log Analytics for full Logic Apps visibility in TigerOps.
#!/bin/bash
# TigerOps — Azure Logic Apps integration setup
LOGIC_APP="my-logic-app"
RESOURCE_GROUP="my-resource-group"
WORKSPACE_ID="/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.OperationalInsights/workspaces/tigerops-workspace"
LA_RESOURCE="/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.Logic/workflows/${LOGIC_APP}"
# Enable diagnostic settings for the Logic App
az monitor diagnostic-settings create \
--name tigerops-logicapp \
--resource "${LA_RESOURCE}" \
--workspace "${WORKSPACE_ID}" \
--metrics '[{"category":"AllMetrics","enabled":true}]' \
--logs '[
{"category":"WorkflowRuntime","enabled":true}
]'
# For Standard Logic Apps (single-tenant), enable additional categories
# az monitor diagnostic-settings create ...
# --logs '[
# {"category":"WorkflowRuntime", "enabled":true},
# {"category":"FunctionAppLogs", "enabled":true}
# ]'
echo "Logic Apps diagnostics enabled for: ${LOGIC_APP}"
echo "Run history and action-level events will appear in TigerOps within 3 minutes"Common Questions
Does TigerOps support both Consumption and Standard Logic Apps?
Yes. TigerOps monitors both Consumption (multi-tenant) and Standard (single-tenant) Logic Apps. Standard tier workflows emit the same Azure Monitor metrics with additional stateful and stateless workflow distinction.
How granular are action-level metrics in TigerOps?
Action-level metrics come from the WorkflowRuntime diagnostic log category streamed to Log Analytics. TigerOps parses these logs to surface per-action success rates, execution durations, and error messages for each run.
Can I alert on specific workflow failure patterns?
Yes. TigerOps supports alert rules based on action name, error code, and connector type. You can create a targeted alert that fires only when a specific connector such as a Service Bus or Salesforce action fails repeatedly.
How does TigerOps handle Logic Apps that run infrequently?
For low-frequency workflows, TigerOps switches from rate-based to count-based alerting. Instead of alerting on failure rate percentage, you configure an absolute failure count threshold per time window suitable for your run frequency.
Can TigerOps trace end-to-end business processes that span multiple Logic Apps?
Yes. If you propagate a correlation ID through your Logic Apps workflow chain, TigerOps can stitch together run events across multiple workflows to show the full end-to-end business process execution timeline and identify where failures or delays occur.
Keep Your Business Automation Workflows Healthy
Workflow run tracking, action success rates, and AI anomaly detection for Azure Logic Apps. Connect in 5 minutes.