AZ

azure-observability-baseline

Wires Application Insights and Log Analytics to Odoo for Azure-based observability.

Install

mkdir -p .claude/skills/azure-observability-baseline && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10281" && unzip -o skill.zip -d .claude/skills/azure-observability-baseline && rm skill.zip

Installs to .claude/skills/azure-observability-baseline

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Wire Azure-native monitoring for Odoo on ACA with Application Insights, Log Analytics, and alert rules
102 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Instrument Odoo on ACA
  • Setup monitoring alerts
  • Configure App Insights
  • Route PG logs to Log Analytics

How it works

The skill patches Bicep modules to bind Application Insights to the ACA environment and configures diagnostic settings for PostgreSQL Flexible Server.

Inputs & outputs

You give it
Odoo ACA environment configuration
You get back
Instrumented ACA environment with alert rules and diagnostic settings

When to use azure-observability-baseline

  • Instrument Odoo on ACA
  • Setup monitoring alerts
  • Configure App Insights

About this skill

azure-observability-baseline

Impact tier: P1 -- Operational Readiness

Purpose

Close the observability gap where the Odoo runtime lacks Azure-native monitoring. The benchmark audit found: no Application Insights instrumentation, no Log Analytics workspace, no Azure Monitor alert rules, and residual Docker/Prometheus assumptions in documentation that do not apply to the ACA runtime.

When to Use

  • Instrumenting Odoo on Azure Container Apps for the first time.
  • Replacing Docker-centric monitoring (Prometheus, cAdvisor) with Azure-native stack.
  • Setting up alert rules for Odoo health, PG health, and ACA scaling events.
  • Preparing for go-live observability readiness.

Required Evidence (inspect these repo paths first)

PathWhat to look for
infra/azure/modules/app-insights.bicepApp Insights resource, connection string output
infra/azure/odoo-runtime.bicepACA env diagnostic settings, App Insights binding
infra/azure/main.bicepLog Analytics workspace, module wiring
infra/ssot/azure/resources.yamlLog Analytics, App Insights entries
docs/runbooks/ODOO18_GO_LIVE_CHECKLIST.mdMonitoring/alerting line items
docs/audits/ODOO_AZURE_ENTERPRISE_BENCHMARK.mdObservability gap row

Microsoft Learn MCP Usage

Run at least these three queries:

  1. microsoft_docs_search("Azure Container Apps Application Insights monitoring") -- retrieves how to bind App Insights to ACA environment.
  2. microsoft_docs_search("Azure Monitor alert rules container apps CPU memory") -- retrieves alert rule configuration for ACA metrics.
  3. microsoft_docs_search("Azure Log Analytics workspace diagnostic settings PostgreSQL") -- retrieves how to route PG Flexible Server logs to Log Analytics.

Optional:

  1. microsoft_code_sample_search("bicep application insights log analytics workspace", language="bicep")
  2. microsoft_docs_fetch("https://learn.microsoft.com/en-us/azure/container-apps/observability")

Workflow

  1. Inspect repo -- Read Bicep modules for existing App Insights and Log Analytics resources. Check if ACA environment has appInsightsConfiguration. Search for any Prometheus/Docker monitoring references to remove.
  2. Query MCP -- Run the three searches. Capture App Insights connection string binding for ACA, alert rule metric names, PG diagnostic categories.
  3. Compare -- Identify: (a) Does a Log Analytics workspace exist in Bicep? (b) Is App Insights connected to ACA? (c) Are alert rules defined? (d) Are there stale Prometheus references?
  4. Patch -- Update Bicep:
    • Create Log Analytics workspace if missing.
    • Create App Insights connected to that workspace.
    • Bind App Insights to ACA environment via appInsightsConfiguration.
    • Add diagnostic settings for PG Flexible Server.
    • Add alert rules: ACA CPU > 80%, ACA memory > 80%, PG connections > 80%, Odoo health check failure.
    • Remove Docker/Prometheus monitoring references from docs.
  5. Verify -- Bicep lints clean. SSOT updated. Go-live checklist has monitoring items. No Prometheus/Docker monitoring references remain.

Outputs

FileChange
infra/azure/modules/app-insights.bicepApp Insights + Log Analytics
infra/azure/odoo-runtime.bicepACA App Insights binding
infra/azure/modules/postgres-flexible.bicepDiagnostic settings
infra/azure/modules/alerts.bicepAlert rules (new file)
infra/ssot/azure/resources.yamlLog Analytics, App Insights entries
docs/runbooks/ODOO18_GO_LIVE_CHECKLIST.mdMonitoring verification steps
docs/evidence/<stamp>/azure-observability-baseline/Bicep diffs, MCP excerpts

Completion Criteria

  • Log Analytics workspace exists in Bicep with 30-day retention minimum.
  • Application Insights is created and connected to Log Analytics.
  • ACA environment has appInsightsConfiguration.connectionString set.
  • PG Flexible Server has diagnostic settings routing to Log Analytics.
  • At least 4 alert rules defined (CPU, memory, PG connections, health check).
  • No Prometheus, Grafana, or cAdvisor references remain in docs/runbooks/.
  • Evidence directory contains Bicep diffs and MCP query excerpts.

When not to use it

  • Environments with legacy Docker-centric monitoring
  • Production systems without Bicep infrastructure

Prerequisites

Azure Container AppsBicep modulesLog Analytics workspace

Limitations

  • Requires Bicep-based infrastructure
  • Requires 30-day Log Analytics retention

How it compares

It replaces manual Prometheus/Docker monitoring with native Azure Monitor and Log Analytics integration.

Compared to similar skills

azure-observability-baseline side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
azure-observability-baseline (this skill)04moNo flagsIntermediate
azure-functions105moReviewIntermediate
azure-deployment-preflight76moReviewAdvanced
appinsights-instrumentation67moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

azure-functions

aj-geddes

Create serverless functions on Azure with triggers, bindings, authentication, and monitoring. Use for event-driven computing without managing infrastructure.

10104

azure-deployment-preflight

github

Performs comprehensive preflight validation of Bicep deployments to Azure, including template syntax validation, what-if analysis, and permission checks. Use this skill before any deployment to Azure to preview changes, identify potential issues, and ensure the deployment will succeed. Activate when users mention deploying to Azure, validating Bicep files, checking deployment permissions, previewing infrastructure changes, running what-if, or preparing for azd provision.

746

appinsights-instrumentation

github

Instrument a webapp to send useful telemetry data to Azure App Insights

66

skypilot-multi-cloud-orchestration

davila7

Multi-cloud orchestration for ML workloads with automatic cost optimization. Use when you need to run training or batch jobs across multiple clouds, leverage spot instances with auto-recovery, or optimize GPU costs across providers.

10

aspire

davidortinau

**WORKFLOW SKILL** - Orchestrates Aspire applications using the Aspire CLI and MCP tools for running, debugging, deploying, and managing distributed apps. USE FOR: aspire run, aspire stop, aspire deploy, start aspire app, aspire describe, list aspire integrations, debug aspire issues, view aspire lo

00

skill-aks-health

microsoft

[Skill] aks, aks health, cluster health, node pool, activity logs - Inspect Koji AKS cluster health, node pool status, autoscaling, activity logs, deployment failures, and Azure control-plane operations.

00

Search skills

Search the agent skills registry