For any monitoring and diagnostics solution, it is important to provide visibility into the transaction execution across multiple components.

I was thinking how to improve querying experience in Application Insights Analytics.

Application Insights makes automatic ip lookup for your telemetry. Geo information can be quite useful for monitoring, troubleshooting and usage scenarios.

Sometimes you need to send event to Application Insights from the command line and you cannot download the ApplicationInsights.

You may have many environments where your application is running. For every environment you will create a separate Application Insights resource so you can set up access and billing for the production telemetry differnetly from the QA environment.

Sometimes Application Insights wouldn’t track web requests made with the bad routes resulting in the response code 404.

Small tip on how to enable Application Insights Live Metrics from code.

Imagine you run a high load web application. If this application should be accessible from the different domains you need to configure your server to correctly respond to OPTIONS requests.

I lost track of what deployed in staging slot of a cloud service once.

Update @ Feb 2019: I was asked to point to the fact, that this DYI project is not needed as this feature is supported natively by Azure Monitor.