How microsoft/docker-provider works
Project type and purpose
• This is a “Container Monitoring Agent” project for Azure Monitor. It builds and packages both Linux and Windows agents that run in Kubernetes clusters (AKS, Arc-enabled, on-prem) to collect logs/metrics from containers and forward them to Azure Monitor (Log Analytics and Metrics).
File structure
• Top-level folders:
• .pipelines – Azure DevOps CI/CD definitions (build/test/release).
• build – scripts/Makefiles to compile and bundle Linux/Windows installers and shared objects.
• charts – Helm charts for deploying the agent in non-AKS clusters.
• alerts – curated alert rule JSONs (ARM).
• kubernetes – Dockerfiles + build/publish scripts and entrypoint scripts for Linux/Windows agent container images.
• scripts – onboarding, troubleshoot, preview scripts using Azure CLI/ARM/Bicep/Terraform to set up DCR, Workspace RBAC, Azure Policy, etc.
• source/plugins – the core agent “plugins”:
– go/ – out_oms plugin and extension binaries in Go
– ruby/ – in/out/filter plugins in Ruby, ApplicationInsights client, telemetry channel
• test – unit, e2e (sonobuoy, pytest, ginkgo), scenario, scale tests.
README for additional insights
• Describes the dual-agent (Linux + Windows) architecture, prerequisites, build steps (Go, .NET Core, Docker), source layout, pipeline usage, and deployment via Kubernetes YAML/Helm and Azure DevOps release pipelines.