Azure Monitor pricing

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.

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.

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.

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:

• Enterprise Dev/Test
• Pay-As-You-Go Dev/Test

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

The migrated alert rules and corresponding migrated action groups (email, webhook or LogicApp) will remain free of charge. The functionality you had with classic alerts including the ability to edit the threshold, aggregation type,and the aggregation granularity will continue to be available for free with your migrated alert rule. However, if you edit the migrated alert rule to use any of the new alert platform features, notifications or action types, a corresponding charge will apply. The following are examples of cases where you will incur a charge for your alert rule:

• Any new (non-migrated) alert rule created beyond free units, on the new Azure Monitor platform
• Any data ingested and retained beyond free units included by Azure Monitor
• Any multi-test web tests executed by Application Insights
• Any custom metrics stored beyond free units included in Azure Monitor
• Any migrated alert rules that are edited to use newer metric alert features such as frequency, multiple resources/dimensions, Dynamic Thresholds, changing resource/signal and so on
• Any migrated action groups that are edited to use newer notifications, or action types such as SMS, Voice Call and/or ITSM integration

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.