Azure Blob Storage Integration
Storage account metrics, transaction rates, and availability monitoring for Azure Blob Storage. Detect availability degradation and unexpected egress cost spikes before they impact operations.
How It Works
Assign Monitoring Reader
Grant the TigerOps Service Principal the Monitoring Reader role on the storage account resource group. TigerOps does not need storage data plane access — only Azure Monitor metrics.
Enable Storage Diagnostics
Turn on Diagnostic Settings for the Blob service endpoint to stream StorageRead, StorageWrite, and StorageDelete metric categories to a Log Analytics workspace.
Configure Account Monitoring
Add your storage account name and resource group to TigerOps. The integration auto-discovers all containers and begins tracking transaction rates and availability within minutes.
Set Availability Alerts
Define availability SLOs and egress thresholds per storage account. TigerOps alerts on availability drops below your SLO and forecasts egress cost growth trends.
What You Get Out of the Box
Transaction Rate Monitoring
Blob read, write, delete, and list transaction counts and success rates per container and operation type. Identify which containers drive the most API cost and latency.
Availability Tracking
Storage account availability percentage and service-level availability for Blob, Queue, Table, and File services. Detect availability degradation within seconds of it occurring.
Ingress & Egress Monitoring
Byte-level ingress and egress rates per storage account and per operation. TigerOps forecasts monthly egress costs and alerts when daily egress exceeds your configured budget.
End-to-End Latency
SuccessE2ELatency and SuccessServerLatency percentiles per API operation. Distinguish between network latency and server-side processing latency to target optimization efforts correctly.
Capacity & Growth Trends
Used capacity per container tier (Hot, Cool, Archive), blob count growth, and snapshot storage consumption. Plan tier migrations before storage costs exceed budget.
AI Anomaly Detection
TigerOps AI baselines transaction patterns per container and flags unusual read spikes, unexpected delete surges, or availability dips with contextual root cause analysis.
Enable Blob Storage Diagnostics
Stream transaction metrics and storage analytics logs to Log Analytics for full Blob Storage visibility in TigerOps.
#!/bin/bash
# TigerOps — Azure Blob Storage integration setup
STORAGE_ACCOUNT="mystorageaccount"
RESOURCE_GROUP="my-resource-group"
WORKSPACE_ID="/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.OperationalInsights/workspaces/tigerops-workspace"
# Enable diagnostics on the Blob service endpoint
az monitor diagnostic-settings create \
--name tigerops-blob-diagnostics \
--resource "/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.Storage/storageAccounts/${STORAGE_ACCOUNT}/blobServices/default" \
--workspace "${WORKSPACE_ID}" \
--metrics '[
{"category":"Transaction","enabled":true,"retentionPolicy":{"days":30,"enabled":true}},
{"category":"Capacity","enabled":true,"retentionPolicy":{"days":30,"enabled":true}}
]' \
--logs '[
{"category":"StorageRead", "enabled":true},
{"category":"StorageWrite", "enabled":true},
{"category":"StorageDelete", "enabled":true}
]'
# Also enable on the storage account level
az monitor diagnostic-settings create \
--name tigerops-storage-account \
--resource "/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.Storage/storageAccounts/${STORAGE_ACCOUNT}" \
--workspace "${WORKSPACE_ID}" \
--metrics '[{"category":"Transaction","enabled":true}]'
echo "Blob Storage diagnostics enabled for: ${STORAGE_ACCOUNT}"Common Questions
Does TigerOps support Azure Data Lake Storage Gen2?
Yes. ADLS Gen2 is built on Azure Blob Storage and exposes the same Azure Monitor metric categories. TigerOps monitors both flat-namespace Blob Storage and hierarchical-namespace ADLS Gen2 accounts with the same integration.
Can TigerOps alert on storage availability drops?
Yes. The Availability metric in Azure Monitor measures the percentage of successful requests to the storage service. TigerOps evaluates this metric every minute and fires an alert when availability drops below your configured threshold.
How does TigerOps track per-container metrics?
Azure Monitor emits storage metrics at the account level with an optional split by API name and geo-type. For per-container granularity, TigerOps supplements account-level metrics with Storage Analytics logs when enabled.
Does TigerOps support GRS and ZRS storage accounts?
Yes. TigerOps monitors Locally Redundant (LRS), Zone Redundant (ZRS), Geo-Redundant (GRS), and Read-Access Geo-Redundant (RA-GRS) storage accounts. For RA-GRS accounts, secondary endpoint availability is tracked separately.
Can I get alerts when egress costs are trending high?
Yes. TigerOps tracks daily egress byte totals and projects monthly costs using current Azure pricing for your storage region. Alerts fire when the projected monthly egress cost exceeds a threshold you configure in TigerOps.
Complete Visibility Into Azure Blob Storage
Transaction rates, availability tracking, and egress cost forecasting for Azure Blob Storage. Connect in 5 minutes.