This is a question that I’ve received many times and also this morning I had a discussion with a partner about that (and that’s the reason for this quick post).
Using Azure Application Insights for monitoring your Dynamics 365 Business Central SaaS tenant is a must in my opinion, but Application Insights is not a totally free service. Application Insights cost is normally very low and you can monitor it by going on the Azure Portal, select your instance and then in the Configure section select Usage and estimated costs:
From here you can see the details of how much your Application Insights instance costs to you for the current month (you pay for the data ingested):
and you can see the details of the volume trend for your telemetry data:
If you want to limit the amount of data ingested on your Application Insights instance, you can configure your daily data volume cap. The cap is normally set to 100 GB per day and it can be raised up to a maximum of 500 GB per day:
Remember also that Application Insights includes 90 days of data retention as default and longer retention will incur on additional charges. You can specify how many days of retention you want for your instance in the Data retention panel:
If you want to have the complete history of your telemetry data, you can also export them. For exporting, you can:
With Continuous Export the events you see in the Application Insights portal can be exported to storage in Microsoft Azure in JSON format. From there, you can download your data and write whatever code you need to process it.
To add a continuous export process, you need to select a storage container and then you can select the telemetry data types you want to export:
Remember that by default, the storage location will be set to the same geographical region as your Application Insights resource. If you store in a different region, you may incur on transfer charges.
Once you’ve created your export, newly ingested data will begin to flow to Azure Blob storage. Continuous export will only transmit new telemetry that is created/ingested AFTER continuous export was enabled. Any data that existed prior to enabling continuous export will not be exported, and there is no supported way to retroactively export previously created data using continuous export.
After the export configuration, you can analyze the JSON files that you have in your configured Blob storage with the tool you want.
Hoping to have answered some received questions more clearly now…