Exam AZ-400 topic 2 question 33 discussion

1. Disable adaptive sampling 2. Modify usage and estimated costs settings https://learn.microsoft.com/en-us/azure/azure-monitor/app/sampling#types-of-sampling Ingestion sampling happens at the Application Insights service endpoint. It discards some of the telemetry that arrives from your app, at a sampling rate that you set. It doesn't reduce telemetry traffic sent from your app, but helps you keep within your monthly quota. The main advantage of ingestion sampling is that you can set the sampling rate without redeploying your app. Ingestion sampling works uniformly for all servers and clients, but it doesn't apply when any other types of sampling are in operation. https://learn.microsoft.com/en-us/azure/azure-monitor/app/sampling#ingestion-sampling Ingestion sampling doesn't operate while adaptive or fixed-rate sampling is in operation. Adaptive sampling is enabled by default when the ASP.NET SDK or the ASP.NET Core SDK is being used, or when Application Insights is enabled in Azure App Service or by using Application Insights Agent.

applicationinsights.config is not available on .NET Core, as this link says: https://learn.microsoft.com/en-us/azure/azure-monitor/app/configuration-with-applicationinsights-config "The ApplicationInsights.config and .xml instructions don't apply to the .NET Core SDK. To configure .NET Core applications, follow the instructions in Application Insights for ASP.NET Core applications." If you follow the link on the text above, the next article says: "The Application Insights SDK for ASP.NET Core supports both fixed-rate and adaptive sampling. By default, adaptive sampling is enabled." Therefore you need to disable adaptive sampling, so the first box is incorrect

Following the URL provided by @zellck: 1. https://learn.microsoft.com/en-us/azure/azure-monitor/app/sampling#types-of-sampling The main advantage of ingestion sampling is that you can set the sampling rate without redeploying your app. Ingestion sampling works uniformly for all servers and clients, but it doesn't apply when any other types of sampling are in operation. => we have to disable adaptive sampling, because it is set by default -> Adaptive sampling is enabled by default when you use the ASP.NET SDK or the ASP.NET Core SDK, and is also enabled by default for Azure Functions. Scrolling down on this page to title Ingestions sampling we will see that ingestions sampling rate is set in the Usage and estimated costs page. Correct answers are: 1. Disable adaptive sampling 2. Modify usage and estimated costs settings

Fixed-rate sampling is available in recent versions of the Application Insights SDKs for ASP.NET, ASP.NET Core, Java (both the agent and the SDK), JavaScript, and Python. https://learn.microsoft.com/en-us/azure/azure-monitor/app/sampling

from your code repository of webapp1. Disable adaptive sampling, then you can set a fixed sampling percentage of telemetry data collected by Azure Application Insights. You can do it modifying sampling rate telemetry: 1. appsettings.json -> .NET core applications 2. ApplicationInsights.config -> .NET Framework application 3. set up configuration on Azure Application Insights from AppInsights1. Modify the Usage and estimated costs settings, modify the sampling rate of telemetry data.

Yes for the first box we need to disable adaptive sampling. and for the second box it would be configure dynamic export for .Net Core application. https://learn.microsoft.com/en-us/azure/azure-app-configuration/enable-dynamic-configuration-dotnet-core

1st box should be disable adaptive sampling.. please see the note from MS site about adaptive sampling.. Adaptive sampling automatically adjusts the volume of telemetry sent from the SDK in your ASP.NET/ASP.NET Core app, and from Azure Functions. This is the default sampling when you use the ASP.NET or ASP.NET Core SDK. Adaptive sampling is currently only available for ASP.NET server-side telemetry, and for Azure Functions. Source: https://learn.microsoft.com/en-us/azure/azure-monitor/app/sampling?tabs=net-core-new

Modify ApplicationInsights.config: You can modify the ApplicationInsights.config file to adjust the sampling rate as needed without having to redeploy webapp1. Modify the Usage and estimated costs settings: You can modify the sampling rate of the telemetry data processed by AppInsights1 from the Usage and estimated costs settings. This will allow you to adjust the sampling rate without having to redeploy webapp1

got this in 02 March 2023 exams. scored 870 marks.

ApplicationInsights.config is a xml file. This file can be used to configure sampling rate. One of the reason of sampling is reducing cost involved in storing metrics data.By sampling instead of storing large data that can be costly, we are actually storing samples of data , which can be a cheaper option. And when we want to sample data , it means we are reducing usage and estimated cost

Pretty confusing question, Ingestion sampling can help us modify sampling rate without modifying/redeploying app. So we can disable adaptive sampling which will in turn enable ingestion sampling, Moreover, .NET Core does not have ApplicationInsights.config, it has appsettings.json-->Startup.cs But I believe most of us would disable adaptive sampling through the portal and not through web app repo, correct me if I'm wrong

Got this Feb 2023

came up in my exam (febr 2023)

As this is a .NET Core app, all the options for the first blank seems to be invalid because .NET Core apps do not have ApplicationInsights.config files. Instead, the settings have to be changed in Program.cs file or appsettings.json. Reference: https://learn.microsoft.com/en-gb/azure/azure-monitor/app/sampling?tabs=net-core-new#types-of-sampling

Data sampling is to be configured in Usage and estimated costs in Application Insights.