Azure Container Instances Integration
Container group metrics, restart counts, and resource utilization for Azure Container Instances. Detect crash loops and resource exhaustion before they disrupt your containerized workloads.
How It Works
Create a Service Principal
Register an Azure Service Principal with Monitoring Reader on the resource group containing your Container Instance groups. TigerOps uses this to query Azure Monitor for container-level metrics.
Enable Diagnostic Settings
Configure Diagnostic Settings on each Container Group to stream ContainerInstanceLog and ContainerEventLog categories to a Log Analytics workspace for event and restart tracking.
Tag Container Groups
Apply environment and application tags to your Container Groups in Azure. TigerOps uses these tags to group containers in dashboards and route alerts to the correct team channels.
Configure Restart Alerts
Set restart count thresholds per container group. TigerOps fires alerts the moment restart counts exceed normal operational limits and includes the container exit code for fast diagnosis.
What You Get Out of the Box
Container Group CPU & Memory
Real-time CPU usage percentage and memory usage in bytes per container within a group. Compare actual resource consumption against requested limits to right-size your container definitions.
Restart Count Tracking
Container restart counts with exit code history and restart timestamps. TigerOps distinguishes between OOMKill restarts, process crashes, and health probe failures for accurate root cause identification.
Network I/O Metrics
Bytes received and transmitted per container group with per-second rate calculations. Monitor bandwidth consumption for data-intensive container workloads and detect unexpected egress.
Container Lifecycle Events
Container start, stop, and pull events from ContainerEventLog. Track how long image pulls take, monitor container initialization duration, and detect failed start events.
Multi-Container Group Visibility
Side-by-side resource utilization for all containers within a group. Identify which sidecar or init container is consuming disproportionate CPU or memory within a shared group.
AI Crash Loop Detection
TigerOps AI identifies crash loop patterns by analyzing restart frequency, exit codes, and memory usage. It correlates container crashes with image deployments, config changes, or downstream dependency failures.
Container Group ARM Template with Diagnostics
Deploy a Container Group with Log Analytics diagnostics pre-wired for TigerOps monitoring.
// Bicep — Azure Container Group with TigerOps diagnostics
param location string = resourceGroup().location
param workspaceId string
resource containerGroup 'Microsoft.ContainerInstance/containerGroups@2023-05-01' = {
name: 'my-container-group'
location: location
properties: {
containers: [
{
name: 'app'
properties: {
image: 'myregistry.azurecr.io/app:latest'
resources: {
requests: { cpu: 1, memoryInGB: 2 }
limits: { cpu: 2, memoryInGB: 4 }
}
ports: [{ port: 8080, protocol: 'TCP' }]
}
}
]
osType: 'Linux'
restartPolicy: 'OnFailure'
diagnostics: {
logAnalytics: {
workspaceId: reference(workspaceId, '2021-06-01').customerId
workspaceKey: listKeys(workspaceId, '2021-06-01').primarySharedKey
logType: 'ContainerInstanceLogs'
}
}
}
}
// Diagnostic settings to stream metrics to Log Analytics
resource diagnostics 'Microsoft.Insights/diagnosticSettings@2021-05-01-preview' = {
name: 'tigerops-aci'
scope: containerGroup
properties: {
workspaceId: workspaceId
metrics: [{ category: 'AllMetrics', enabled: true }]
logs: [
{ category: 'ContainerInstanceLog', enabled: true },
{ category: 'ContainerEventLog', enabled: true }
]
}
}Common Questions
Does TigerOps support both Linux and Windows containers in ACI?
Yes. Azure Container Instances supports both Linux and Windows containers, and TigerOps collects the same Azure Monitor metrics for both. CPU, memory, and network metrics are available regardless of the container OS.
How does TigerOps track container restarts?
TigerOps monitors the RestartCount metric in Azure Monitor, which increments each time a container in the group restarts. Combined with ContainerEventLog events, TigerOps captures the restart timestamp and exit code for each event.
Can I monitor ephemeral ACI containers that run once and exit?
Yes. For short-lived batch containers, TigerOps captures metrics for the duration of the container run and stores them for historical analysis. You can track execution duration, peak CPU, and memory consumption for each run.
Does TigerOps support ACI containers used with virtual nodes in AKS?
Yes. Container groups deployed as virtual nodes from AKS emit the same Azure Monitor metrics as standalone ACI groups. TigerOps correlates ACI burst capacity usage with the AKS cluster metrics for a complete burst-to-cloud picture.
How are Container Instances alerts routed?
TigerOps routes ACI alerts based on the resource group, environment tag, and application tag applied to the container group. You can configure PagerDuty, Slack, Microsoft Teams, or webhook destinations per alert rule.
Full Visibility Into Your Azure Container Instances
Restart tracking, resource utilization, and AI crash loop detection for ACI. Connect in 5 minutes.