slug: microsoft-azure-monitor provider: Azure Monitor generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Software & Technology min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 10 edges: - tag: Autoscale Settings spec_file: microsoft-azure-monitor-autoscale-settings-api-openapi.yml capability_id: BC-4220.50 capability_id_l1: BC-4220 capability_name: Capacity & Performance Management confidence: 0.82 evidence: '"Configure autoscale settings for Azure resources based on metric thresholds, schedules, or predictive rules to automatically adjust resource capacity"; schemas ScaleCapacity, PredictiveAutoscalePolicy' reason: Operations manage auto-scaling policies and capacity profiles for cloud services, which is precisely Capacity & Performance Management (auto-scaling policies, capacity forecasting). - tag: Metrics spec_file: microsoft-azure-monitor-metrics-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.78 evidence: GET /{resourceUri}/providers/Microsoft.Insights/metrics Metrics_List Azure Monitor List metrics for a resource; schemas MetricsResult, TimeSeriesElement, MetricValue reason: Operations retrieve application and resource telemetry metrics/time series — this is production observability (metrics) of running services, matching Observability Management rather than any business-domain capability. - tag: Query spec_file: microsoft-azure-monitor-query-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.78 evidence: GET /workspaces/{workspaceId}/query 'Execute a Log Analytics query'; POST /apps/{appId}/query 'Execute an Application Insights query' reason: Executing log-analytics and app-telemetry queries is log-based observability of the running service; no business-domain reading fits. - tag: Events spec_file: microsoft-azure-monitor-events-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.75 evidence: '"Access Application Insights telemetry data including requests, dependencies, exceptions, traces, and custom events for application performance monitoring"' reason: Queries APM telemetry (requests, dependencies, exceptions, traces) for running applications — observability of the production service rather than product usage analytics. - tag: Logs Ingestion spec_file: microsoft-azure-monitor-logs-ingestion-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.75 evidence: '"Upload logs to a custom table" ... "Sends custom log data to a Log Analytics workspace"' reason: Ingests log telemetry into the monitoring workspace — logs pipeline capability under Observability Management. - tag: Metrics Batch spec_file: microsoft-azure-monitor-metrics-batch-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.75 evidence: POST /subscriptions/{subscriptionId}/metrics:batchGet 'Batch query metrics for multiple resources'; 'retrieving metric values across multiple Azure resources in a single request' reason: Same observability surface as the Metrics tag, batched; it is metric retrieval for monitoring running services. The 'batch' aspect is a delivery optimisation, not a separate capability. - tag: Scheduled Query Rules spec_file: microsoft-azure-monitor-scheduled-query-rules-api-openapi.yml capability_id: BC-4220 capability_id_l1: BC-4220 capability_name: SaaS Platform Operations Management confidence: 0.75 evidence: '''Create and manage log search alert rules that automatically evaluate log queries at regular intervals and fire alerts when conditions are met''' reason: 'Alert-rule management sits between observability (log evaluation) and incident detection; clearly platform operations at L1 but the evidence does not cleanly pick one L2, so L2 is left null. Note: ''alert'' here is monitoring alerting, not financial-crime alerting.' - tag: Diagnostic Settings spec_file: microsoft-azure-monitor-diagnostic-settings-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.72 evidence: '"Configure diagnostic settings to route platform logs and metrics from Azure resources to destinations such as Log Analytics workspaces, Storage Accounts, and Event Hubs"' reason: Routing of platform logs and metrics to analytics destinations is core observability plumbing for the running service; schemas LogSettings/MetricSettings confirm. - tag: Predictive Metrics spec_file: microsoft-azure-monitor-predictive-metrics-api-openapi.yml capability_id: BC-4220.50 capability_id_l1: BC-4220 capability_name: Capacity & Performance Management confidence: 0.72 evidence: '''Configure autoscale settings for Azure resources based on metric thresholds, schedules, or predictive rules to automatically adjust resource capacity''; PredictiveMetric_Get ''Get predictive autoscale metrics''' reason: Predictive autoscale metrics feed capacity forecasting and auto-scaling policies, which is exactly Capacity & Performance Management for a running service. - tag: Data Collection Rules spec_file: microsoft-azure-monitor-data-collection-rules-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.7 evidence: '"data collection rules that define how data is collected, transformed, and routed to destinations within Azure Monitor"; schemas DataSources, DataFlow, Destinations' reason: Configures collection, transformation and routing of operational telemetry (logs/metrics) for monitoring, i.e. Observability Management.