Exam AZ-204 topic 19 question 3 discussion

(∩^o^)⊃━☆

"ITelemetryProcessor" typo, no "n" https://docs.microsoft.com/en-us/azure/azure-monitor/app/api-filtering-sampling#create-a-telemetry-processor-c

look at that s**t man , i've never seen a constructor like that.

1. public class Filter : ITelemetryProcessor 2. private readonly ITelemetryProcessor _next; 3. public (Filter ITelemetryProcessor next) 4. var x = item as RequestTelemetry 5. if(x?.Url.AbsolutePath == "/health") - https://learn.microsoft.com/en-us/azure/azure-monitor/app/api-filtering-sampling?tabs=javascriptwebsdkloaderscript#c - https://learn.microsoft.com/en-us/azure/azure-monitor/app/api-filtering-sampling?tabs=javascriptwebsdkloaderscript#create-a-telemetry-processor-c

The question is not inline with the requirement in the case study text. It should be "Exclude non-user actions from Application Insights telemetry." According to the requirement all health check requests, which is a RequestTelemetry type, for the api should be filtered out by setting the path to "/health" .

The question is so wrong "You need to implement telemetry for non-user actions" that MUST be: "You need to implement telemetry to exclude non-user actions" (according to the requirements). In that case you have to exclude RequestTelemetry in combination with /health

This is chaining of ITelemetryProcessors where the Filter (the one created here) is the first one. The ITelemetryProcessor instance passed in the constructor is the next in the chain. The code checks if the url is /health and it does not do anything otherwise it fowards to the next (which is the one passed in the Constructor). Look at the line: "item as RequestTelemetry" : What kind of people work in Microsoft that will do the casting without checking the instance of the item? No wonder Microsoft things are so buggy

In code, public Filter() not public (Filter ...)

Answer: ITelemetryProcessor, ITelemetryProcessor,ITelemetryProcessor,RequestTelemetry, /health Reference: https://docs.microsoft.com/en-us/azure/azure-monitor/app/api-filtering-sampling public class SuccessfulDependencyFilter : ITelemetryProcessor { private ITelemetryProcessor Next { get; set; } // next will point to the next TelemetryProcessor in the chain. public SuccessfulDependencyFilter(ITelemetryProcessor next) { this.Next = next; } } var requestTelemetry = telemetry as RequestTelemetry;

Yes, you are right. It should be; public Filter (ITelemetryProcessor next)

ITelemetryInitializer: Use telemetry initializers to define global properties that are sent with all telemetry; and to override selected behavior of the standard telemetry modules. For example, the Application Insights for Web package collects telemetry about HTTP requests. By default, it flags as failed any request with a response code >= 400. But if you want to treat 400 as a success, you can provide a telemetry initializer that sets the Success property. ITelemetryProcessor: This technique gives you more direct control over what is included or excluded from the telemetry stream. You can use it in conjunction with Sampling, or separately. To filter telemetry, you write a telemetry processor and register it with the SDK https://github.com/uglide/azure-content/blob/master/articles/application-insights/app-insights-api-filtering-sampling.md

Looks Good