Skip navigation

Azure Monitor pricing

Get the granular, real-time monitoring of data that you need – all in one place

Azure Monitor is a platform capability for monitoring your Azure resources. Azure Monitor allows you to collect granular performance and utilisation data, activity and diagnostics logs, and notifications from your Azure resources in a consistent manner. You can use the Azure portal to view and analyse the monitoring data and set up automated actions based on alerts. In addition, Azure Monitor integrates with other analytics and monitoring tools such as OMS Insight & Analytics, Application Insights and other third-party tools, giving you the flexibility to use this data in different ways.

Pricing details

Log Analytics

Log analytics is billed per gigabyte (GB) of data ingested into the service.

Feature Free units included Price
Data Ingestion 5 GB per month1 $- GB per month
Data Retention 31 days2 $- per GB per month

1The first 5 GB of data ingested to the Azure Log Analytics service every month is offered for free.

2Every GB of data ingested into your Azure Log Analytics workspace will be retained at no charge for the first 31 days.

Please note: Service Map solution is billed for data ingested by the Dependency Agent into the Service Map platform and the Log Analytics service. Data ingested by the Dependency Agent is billed per Log analytics prices listed above. Billing for data ingested into the Service Map platform is not enabled yet and will be billed from 1 December 2018.

Application Insights

Application Insights is billed based on the volume of telemetry data that your app sends and the number of web tests that you choose to run. The telemetry data is billed per Azure Log Analytics data ingestion rates.

Feature Price
Data Ingestion See Azure Log Analytics data ingestion rates above
Data Retention 90 days
Multi-step web tests 3, 4 $- per test per month
Ping web tests4 Free

3Multi-step web tests are prorated daily for each test that is active, independent of the number of locations from which the test is run or the test execution frequency.

4Charges for notifications are separate and charged per pricing below.

Metrics

A metric represents a set of time series. You are billed based on the number of time-series monitored and API calls made.

Currently, there are no charges for metric queries and custom metrics. Charges for metric queries and custom metrics will go into effect on 1 December 2018 and 31 March 2019, respectively.

Feature FREE UNITS INCLUDED Price
Standard metrics5 Unlimited Free
Custom metrics 150 MB per month $0.258/MB: 150-100,000 MB
$0.151/MB: 100,000-250,000 MB
$0.061/MB: above 250,000 MB
Metric queries6 1,000,000 standard API calls per month $-/1,000 standard API calls

5Standard metrics are available for free and include select metrics originating from Azure resources, services and first-party solutions. See the list of standard metrics.

6Metric queries are charged based on the number of standard API calls. A standard API call is a call that analyses 1,440 data points (1,440 is also the total number of data points that can be stored per metric per day). If an API call analyses more than 1,440 data points, then it will count as multiple standard API calls. If an API call analyses less than 1,440 data points, it will count as less than one API call. The number of standard API calls is calculated every day as the total number of data points analysed per day divided by 1,440. )

  • Metrics are available for a 90-day period at no charge. To retain metrics data beyond the 90-day period, metrics data can be routed to a storage account, Azure Log Analytics workspace or event hubs. Corresponding charges apply for storage, Log Analytics and event hubs, respectively. In addition, metric queries are charged for the corresponding API calls required to route data.

Examples

  1. An API call that analyses 2,000 data points will count as 2,000/1,440 = 1.4 standard API calls.
  2. An API call that analyses 200 data points will count as 200/1,440 = 0.1 standard API calls.
  3. A scenario tracking five metrics with one-minute granularity from 100 VMs a day will result in 720,000 data points, which translates to (720,000/1,440) 500 standard API calls per day.

Health monitoring

Health monitoring is billed for the number of health criteria metric time-series monitored for an Azure resource.

Prior to 1 December 2018, there are no charges for health monitoring. On 1 December 2018, charges for health monitoring will go into effect per the pricing plan below.

Feature FREE UNITS INCLUDED Price
Health criteria None $- per monitored metric time-series per month

Alert rules

An alert rule is charged based on the type and number of signals that it monitors. A signal can be a resource metric, a log or an activity log. The cost of an alert rule that monitors multiple signals is the sum of the cost of monitoring each signal.

Alert signal FREE UNITS INCLUDED Price
Metrics7, 8 10 monitored metric time-series per month $- per metric time-series monitored per month
Log None 15-min interval (or greater): $- per log monitored per month
10-min interval: $- per log monitored per month
5-min interval: $- per log monitored per month
Activity Logs Unlimited Free

7Price listed here represents the price of an alert rule monitoring a single metric time-series originating from a single resource.

8Pricing is applicable to the new generation metric alert rules available under Alerts. Previous generation alert rules (Alerts Classic) will continue to be available at no charge

  • There is a configuration limit of 100 metric time-series alerts, 100 activity log alerts and 10 action groups per subscription. Contact Azure support to increase the limit.
  • Activity logs are available for a 90-day period at no charge. To retain activity log data beyond the 90-day period, activity log data can be routed to a storage account or event hubs. Corresponding charges will apply for storage and event hubs, respectively. No charges are incurred for API calls to pull activity log data.
  • Alerts offered as part of Azure Security Center (ASC) are not currently charged

Examples

  1. The price of an alert rule which monitors the CPU utilisation and RAM usage (i.e. 2 metric time-series) for 10 VMs, can be calculated as,
    • (10 VMs * 2 metric time-series per VM – 10 free units) * $- per metric time-series alert rule per month = $- per month
  2. The price of an alert rule which queries 1 Log analytics workspace for a ‘404-error’ event every 15 minutes can be calculated as,
    • 1 workspace * 1 log alert query * $- per log alert rule per month = $- per month

Notifications

Notifications are sent based on when an Alert rule triggers. You are billed based on the type and number of notifications you choose to send.

Feature FREE UNITS INCLUDED Price
ITSM connector create or update event9 1,000 events per month $-/1,000 events
Emails 1,000 emails per month $-/100,000 emails
Push notification (to Azure Mobile App) 1,000 notifications per month $-/100,000 notifications
Web hooks 100,000 web hooks per month $-/1,000,000 web hooks
Voice call 10 voice calls per month $-/voice call
SMS See next table for SMS pricing
Country Code FREE UNITS INCLUDED Price
United States (+1) 100 SMS per month $-/SMS
Australia (+61) $-/SMS
Brazil (+55) $-/SMS
China (+86) $-/SMS
France (+33) $-/SMS
Germany (+49) $-/SMS
Hong Kong (+852) $-/SMS
India (+91) $-/SMS
Ireland (+353) $-/SMS
Japan (+81) $-/SMS
Netherlands (+31) $-/SMS
Singapore (+65) $-/SMS
South Africa (+27) $-/SMS
South Korea (+82) $-/SMS
United Kingdom (+44) $-/SMS

9ITSM connector leverages Log Analytics for storage of logs related to daily syncs, ticket creation and updates. Logs ingested are billed at standard Log Analytics rates above.

Diagnostic Logs

Diagnostic logs can be routed to a storage account, Log Analytics workspace or event hub. Corresponding charges will apply for storage, Log Analytics and event hubs, respectively.

Support and SLA

  • SLA for individual features is applicable once the corresponding pricing model has been implemented. Learn more

Log Analytics FAQs

  • Customers who started using Log Analytics on the free tier before 2 April 2018 can continue to stay on the old free tier. The old free tier has a 500 MB limit on the amount of data collected daily and doesn’t allow for data retention periods that are longer than 7 days. The new pricing model does not have any limits on the amount of data collected daily and allows you to retain your log data for up to two years. Customers on the old pricing model can switch at any time to the new pricing model above.

  • Yes. You can remain on the Insight & Analytics per-node pricing model to use Log Analytics.

  • To estimate the effect of the per GB pricing model, visit our documentation on the Usage and estimated costs page. Note that in the new pricing model, data ingestion and retention are both priced differently depending on the region in which you have your Log Analytics workspace. Make sure that you account for this when making any estimated cost comparison. Also, if you purchased the OMS Suite, make sure that you talk to your account representative to fully understand the impact of any change.

  • Please follow the steps listed on the documentation page to move to the new pricing model.

  • Yes, Enterprise Agreement (EA) customers on the Insight & Analytics per-node pricing model can continue to access the per-node pricing plans on any new subscriptions that they link to their existing EA.

  • Yes, customers who started using Log Analytics before 1 October 2016 continue to exist on an older pricing model and can switch at any time to the new models above. The pricing models below have not been available to any new workspaces since 1 October 2016.

    Standard Premium
    Daily limit None None
    Retention period 1 month 12 months
    Customise longer retention periods Not available Not available
    Price $2.3 per GB $3.5 per GB
  • You can select a retention period ranging from 30 to 730 days. The retention cost calculation is done on a daily granularity based on the monthly price per GB being stored beyond the 31 days of included retention.

Application Insights FAQs

  • The older pricing model offered two tiers – Basic and Enterprise. From 2 April 2018, customers on the Basic tier will get billed using the above pricing model which offers more features at no incremental cost. Customers on the Basic tier will continue to receive 1 GB per resource per month of free data allowance in addition to the 5 GB per subscription per month of free data allowance offered by the Azure Log Analytics service. From 2 April 2018, Basic customers will also have access to Continuous Export and the Application Insights Connector for Operations Management Suite Log Analytics. Also, note that in the new plan, you can use your monthly credit as a Visual Studio subscriber to pay for Application Insights.

    Enterprise tier customers can continue to stay on the older pricing model or can switch at any time to the above pricing model. All customer subscriptions with Application Insights enabled before 2 April 2018 are billed $- per GB for any data ingested by Application Insights. However, the only situation where this is advantageous is when you’ve purchased the OMS. Suite. In this case, each purchased unit of the Operations Management Suite E1 and E2 plans includes an entitlement to one node of the Enterprise tier of Application Insights. Each Application Insights Enterprise node includes up to 200 MB of Application Insights data ingested per day, with 90-day data retention at no additional cost.

    Enterprise
    Base monthly price $- per node
    Included data 200 MB per node each day
    Additional data $- per GB
    Data retention (raw and aggregated data) 90 days
    Application Performance Management (APM) and Analytics features Included
    Continuous export Unlimited
    Multi-step web tests $- per test per month
  • No. Customers who started using Application Insights before 2 April 2018 will continue to be billed $- per GB for any data ingested by Application Insights.

  • You can set a daily cap on the amount of data that Application Insights will accept from your application, allowing you to control your costs. After the daily cap has been reached, excess data will be ignored for the remainder of the day (in UTC time), and then will resume normally at the start of the next day.

    Additionally, you can use sampling to reduce the amount of data you send to Application Insights from your application.

    Learn more about managing pricing and data volume in Application Insights.

  • A node is a physical or virtual machine, or a Platform-as-a-Service (PaaS) instance that's hosting your app. For example, if your application runs on three Azure App Service instances and one virtual machine, then you have four nodes hosting your application. We count the number of distinct nodes sending telemetry data each hour. If a node doesn’t send any telemetry during a particular hour, then it’s not counted. The monthly per-node pricing above assumes that a node is sending telemetry every hour of the month, so if there are periods of inactivity for your application during the month, the actual charge will be lower.

    As your application scales up or down, such as adding additional web servers during peak periods of activity, Application Insights Enterprise charges will scale up or down as well.

    There are a few situations that are excluded from node counting (though data volume is always counted):

    • Developer workstations running an application during debugging are not counted as nodes.
    • Using the JavaScript browser client SDK (or certain other SDKs that don’t report “roleInstance”) doesn’t count your end-users’ machines as nodes.
    • Using the HockeyApp bridge app doesn’t count each mobile device monitored by HockeyApp as nodes.

    What if I use the same node for multiple applications that I'm monitoring? That’s no problem. We only count the unique nodes sending telemetry data within your Azure subscription (billing account). For instance, if you have five separate websites running on the same physical server, and each website is configured with Application Insights Enterprise (charged per node), then collectively these will count as one node.

    You can also have applications using Application Insights Basic (charged per GB) in the same Azure subscription, and this won’t affect the node counting for the applications that use Application Insights Enterprise.

    How does the daily 200 MB data work in Application Insights Enterprise? When you choose the Enterprise pricing option, your application gets a daily allowance of data based on the number of nodes sending telemetry. So, if you have five nodes sending data, you will have a pooled allowance of 1 GB per day for your application (as defined by the Application Insights resource you set up). It doesn’t matter if certain nodes are sending more data than other nodes because the included data is shared across all nodes for a given Azure subscription. If, on a given day, you send more data than is included in your daily data pool, the per-GB overage data charges apply. Unused data within your daily allowance doesn’t roll over.

    The daily pooled data allowance is calculated as the number of hours in the day that each node is sending telemetry divided by 24 times 200 MB. So, if you have four nodes sending telemetry during 15 of the 24 hours in the day, the included data for that day would be ((4 x 15) / 24) x 200 MB = 500 MB.

    If you choose the Enterprise pricing option for multiple applications within the same Azure subscription, the daily allowance of data will be shared across those applications. This daily allowance is not shared with applications for which you have chosen the Basic pricing option.

  • Yes. Here are the team Dev/Test offers available today:

  • If you have questions about how pricing works for Application Insights, feel free to post a question in our forum.

Alerts FAQs

  • Activity log, service health and resource health alert rules continue to be available at no charge.

  • Alert notifications are charged separately based on the type of notification used.

  • The pricing listed above is applicable to the new Alerts platform. If you transition your existing alert rules from the Classic Alerts platform to the new platform, the pricing listed above will be applicable.

  • Existing OMS Log Alerts customers will not be charged for the first 250 log alert rules. Any alert rules above the 250 log alert rules limit will be billed per the prices listed above.

  • Existing OMS log alert customers can create Azure log alert rules with any frequency up to the 250-log alert rules limit. Log alert rules created beyond the 250-log alert rule limit will be billed per the prices listed above.

  • If you are an existing Application Insights customer, any existing metric and web test alert rules that are migrated to the new Alerts platform will continue to be free. Any new metric and web test alerts will be charged at the applicable rates of a metric alert rule. Application Insights log alert rules will be charged as per pricing above.

Resources

Estimate your monthly costs for Azure services

Review Azure pricing frequently asked questions

Learn more about Azure Monitor

Review technical tutorials, videos and more resources

Added to estimate. Press 'v' to view on calculator View on calculator

Learn and build with $200 in credit, and keep going for free