CuraDevOps

tag: Azure-Monitor · 7 items

  • Platform/SRE — Plan: If you run Azure Container Apps with Log Analytics as the logging destination, Microsoft has marked it legacy and recommends migrating to Azure Monitor; no forced removal date is given, but schedule the migration before it becomes a breaking change.
  • CI/CD — Skip
  • Leader — Skip
2026-10-20 · Azure Updates · source ↗ #azure-monitor#observability#finops
  • Platform/SRE — Plan: This GA feature lets you audit Azure Monitor workspace consumption — identify unused metrics and right-size ingestion this quarter; no forced deadline but directly actionable for cost and hygiene.
  • CI/CD — Skip
  • Leader — Learn: Adds visibility into Azure Monitor spend patterns, useful context for FinOps reviews, but no strategic decision is forced by this release.
  • Signals: GA announcement
2026-10-07 · Azure Updates · source ↗ #aks#azure-monitor#observability
  • Platform/SRE — Plan: The pod name dimension on AKS platform metrics (kube_pod_status_phase and related) is being removed September 30, 2027; audit Azure Monitor dashboards and alerts that rely on per-pod granularity from these metrics and plan migration to aggregate counters or Prometheus-based alternatives before that date.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: deprecation/EOL deadline mentioned: September 30, 2027
  • Platform/SRE — Plan: This GA capability lets platform teams migrate high-volume compliance and audit Azure tables to the lower-cost Auxiliary plan without rebuilding pipelines. Evaluate which existing Log Analytics tables qualify for plan switching this quarter to reduce observability ingestion costs.
  • CI/CD — Skip
  • Leader — Plan: The plan-switching capability is a concrete FinOps lever for reducing Azure Monitor spend on high-volume, rarely-queried compliance logs. Worth scheduling an audit of Log Analytics table plans to identify cost-reduction opportunities within the current planning cycle.
  • Signals: GA announcement
  • Platform/SRE — Plan: If you operate workloads in Azure Government or Azure China, this new GA log tier offers a cheaper ingestion and retention path for high-volume compliance/audit logs — evaluate whether shifting verbose log streams to Auxiliary tables reduces your Monitor costs this quarter.
  • CI/CD — Skip
  • Leader — Learn: Auxiliary Logs adds a cost-effective tier for compliance and audit log retention in sovereign cloud regions; useful context if the org has Azure Government or China footprint and is managing observability spend, but no strategic decision is forced.
  • Signals: GA announcement
  • Platform/SRE — Learn: Teams using Azure Monitor who store high-volume telemetry in Basic or Auxiliary tiers can now query that data through the AI observability agent without changing storage strategy; worth evaluating during next observability stack review.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: GA announcement
  • Platform/SRE — Learn: Preview feature that could eventually simplify cross-platform observability data sharing from Log Analytics into OneLake; no action warranted until GA.
  • CI/CD — Skip
  • Leader — Learn: Worth tracking as a potential data-platform consolidation play for orgs already invested in both Azure Monitor and Microsoft Fabric; pre-GA so no decision needed yet.
  • Signals: pre-GA (alpha/beta/RC/preview)