Azure Monitoring
Azure Monitoring
When you open the page, you can select among the subscriptions you have read access to. For a
selected subscription, you can see:
Triggered alerts and alert sources - This table shows summary counts, alert sources, and how
many times alerts fired for the selected time duration. It applies to both older and newer alerts
Activity Log Errors - If any of your Azure resources log events with error-level severity, you can
view a high-level count and click through to the activity log page to investigate each event.
Azure Service Health - You can see a count of Service Health service issues, planned maintenance
events, and health advisories. Azure Service Health provides personalized information when
problems in the Azure infrastructure impact your services.
Application Insights - See KPIs for each App Insights resource in the current subscription. The
KPIs are optimized for server-side application monitoring across ASP.NET web apps, Java, Node,
and General application types. The KPIs include metrics for request rate, response duration, failure
rate, and availability %.
Azure Monitor enables you to consume telemetry to gain visibility into the performance and health of
your workloads on Azure. The most important type of Azure telemetry data is the metrics (also called
performance counters) emitted by most Azure resources. Azure Monitor provides several ways to
configure and consume these metrics for monitoring and troubleshooting.
All metrics have one-minute frequency (unless specified otherwise in a metric's definition).
You receive a metric value every minute from your resource, giving you near real-time
visibility into the state and health of your resource.
Metrics are available immediately. You don't need to opt in or set up additional diagnostics.
You can access 93 days of history for each metric. You can quickly look at the recent and
monthly trends in the performance or health of your resource.
Some metrics can have name-value pair attributes called dimensions. These enable you to
further segment and explore a metric in a more meaningful way.
Configure a metric alert rule that sends a notification or takes automated action when the metric
crosses the threshold that you have set. Actions are controlled through action groups. Example
actions include email, phone, and SMS notifications, calling a webhook, starting a runbook, and
more. Autoscale is a special automated action that enables you to scale your a resource up and down
to handle load yet keep costs lower when not under load. You can configure an autoscale setting rule
to scale in or out based on a metric crossing a threshold.
Route all metrics to Application Insights or Log Analytics to enable instant analytics, search, and
custom alerting on metrics data from your resources. You can also stream metrics to an Event Hub,
enabling you to then route them to Azure Stream Analytics or to custom apps for near-real time
analysis. You set up Event Hub streaming using diagnostic settings.
Archive the performance or health history of your resource for compliance, auditing, or offline
reporting purposes. You can route your metrics to Azure Blob storage when you configure diagnostic
settings for your resource.
Use the Azure portal to discover, access, and view all metrics when you select a resource and plot
the metrics on a chart. You can track the performance of your resource (such as a VM, website, or
logic app) by pinning that chart to your dashboard.
Query metrics by using the PowerShell cmdlets or the Cross-Platform REST API.
Consume the metrics via the new Azure Monitor REST APIs.
Following is a quick walkthrough of how to create a metric chart by using the Azure portal.
Alert rules
The unified alerts experience uses the following concepts to separate alert rules from alerts while
unifying the authoring experience across different alert types.
Item Definition
Item Definition
You create a new alert rule with the following three steps:
1. Pick the target for the alert.
2. Select the signal from the available signals for the target.
3. Specify the logic to be applied to data from the signal.
This simplified authoring process no longer requires the user to know the monitoring source or
signals supported before selecting an Azure resource. The list of available signals are automatically
filtered based on target resource selected and guides you through defining the logic of the alert rule
Activity log :