FAQ

Log Analytics FAQs

• If I have Insight and Analytics per node pricing, can I continue to stay on that pricing to use Log Analytics?

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

• If I have Insight and Analytics per node pricing plan, how do I know if the new per GB pricing model is better for me?

  To estimate the impact 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. Be sure to account for this in making any estimated cost comparison. Also, if you purchased the OMS Suite, be sure to talk to your account representative, to fully understand the impact of any change.

• If I have Insight and Analytics per node pricing plan, can I access the per node pricing plan on new subscriptions?

  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.

• How is data retention calculated?

  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.

Alerts FAQs

• Is the above pricing applicable to activity log, service health and resource health alert rules?

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

• Is cost of alert notifications (via Azure Action Groups) included in the cost of an Alert rule?

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

• If I am an existing customer on the Classic Alerts platform, is the above Alert rule pricing applicable to me?

  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.

Application Insights FAQs

• How can I control or limit my costs for 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.

• What are nodes and how are how are the per-node data allowances applied under the Application Insights Enterprise pricing option?

  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 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 is shared across those applications. This daily allowance is not shared with applications for which you have chosen the Basic pricing option.