Skip to main content
emnode
Sign up
Learning path

See what Azure is doing

VM insights, metric and log alerts, Application Insights and action groups.

6 lessons·~83 min total

Lessons in this path

  1. 1
    Monitoring AZURE

    Filter resource logs with diagnostic settings and DCR transformations

    One capability across every Azure resource: collect the log categories you actually need to investigate an incident, and drop the noise before it lands in Log Analytics, so you keep the visibility that protects mean-time-to-detect without paying to ingest data nobody will ever query.

    14 min
  2. 2
    Monitoring AZURE

    Switch low-value tables to the Basic logs plan

    One capability across every Log Analytics workspace: keep the verbose, high-volume tables you only ever search during an incident on the discounted Basic plan, so the budget you save funds the analytics-grade visibility that actually shortens your mean time to detect and resolve.

    14 min
  3. 3
    Monitoring AZURE

    Control Log Analytics ingestion and retention costs

    One capability across every workspace: keep ingestion to the data you actually use to run and observe the estate, retain it only as long as it earns its keep, and put a safety net under unexpected spikes, all without going blind to what your services are doing.

    14 min
  4. 4
    Monitoring AZURE

    Alert on Azure Monitor data-ingestion anomalies

    One capability across every Log Analytics workspace: notice when the volume of logs flowing in jumps, collapses or hits a limit, before a runaway bill lands or a blind spot swallows the signal you needed.

    14 min
  5. 5
    Monitoring AZURE

    Keep Traffic Manager endpoint monitoring healthy

    One capability across every Traffic Manager profile: make sure endpoint health monitoring is actually online, because a degraded probe means failover cannot be trusted and you are routing live traffic blind.

    14 min
  6. 6
    Monitoring AZURE

    Allocate and trim AKS spend with Cost Analysis

    One capability for the most opaque line on the bill: turn an AKS cluster from a single undivided charge into cost broken down by namespace and workload, so idle capacity and runaway teams are visible instead of buried.

    13 min