azureblog.co.uk
← AZ-305 study plan
AZ-305 · Design identity, governance, and monitoring solutions

Design logging and monitoring

Recommending a logging solution, routing logs to the right destinations, and choosing monitoring tools.

  • 14 min
  • 3 concepts
  • Try it yourself
  • 4-question check

Learn

As an architect you decide where logs go, how long they're kept, who can see them, and which tools watch them. Good designs keep costs predictable and give operations and security teams what they need.

  1. 1

    Recommend a logging solution

    Use Log Analytics workspaces as the central store. Prefer as few workspaces as possible, usually one per region or per environment, and split only for data sovereignty, billing, or very different access needs. Control access with resource-context (users see logs for resources they can access) or table-level RBAC. Choose table plans: Analytics for frequently queried data, Basic or Auxiliary for high-volume, rarely queried logs. Set retention and long-term retention per table.

    Remember: Fewer workspaces; resource-context access.

  2. 2

    Recommend a solution for routing logs

    Diagnostic settings route platform logs and metrics to Log Analytics (query and alert), Storage (cheap archive), Event Hubs (third-party SIEM or streaming) or partner solutions. Data collection rules route agent data (Azure Monitor Agent) and can filter or transform before ingestion to cut cost. Use Azure Policy (DeployIfNotExists) to apply diagnostic settings at scale.

    Remember: Third-party SIEM: Event Hubs. Archive: Storage. Query: Log Analytics.

  3. 3

    Recommend a monitoring solution

    Azure Monitor for metrics, logs and alerts, with Insights (VM, container, network, storage). Application Insights for application performance with OpenTelemetry. Network Watcher and Connection Monitor for networks. Microsoft Sentinel for security monitoring. Azure Managed Grafana for dashboards. Azure Service Health and Resource Health for platform issues. Use action groups and alert processing rules for routing.

    Remember: Ops: Azure Monitor. Apps: Application Insights. Security: Sentinel.

Where should logs go?

NeedDestination
Query, alert, workbooksLog Analytics workspace
Keep for years cheaplyStorage account (or long-term retention)
Stream to a third-party SIEMEvent Hubs
Security analyticsLog Analytics with Microsoft Sentinel

Try it

Design the log destination for a workload.

This interactive part needs JavaScript.

In the portal

  • WorkspacesAzure portal: Log Analytics workspaces > Create
  • Table plansAzure portal: Log Analytics workspaces > your workspace > Settings > Tables
  • Data collection rulesAzure portal: Monitor > Settings > Data Collection Rules

Key terms

Click a card to see the definition.

Check your understanding

4 questions. Score 80% or more and these skills are marked as confident in your AZ-305 study plan.

  1. Logs must be streamed to a third-party SIEM. Which destination?

  2. How do you apply diagnostic settings to every new resource?

  3. How do you cut ingestion cost for noisy logs?

  4. What's the general guidance on workspace count?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.