Create Azure Monitor Alert Rules with Azure Bicep Paid Members Public
Previously, I wrote a well-received popular blog post about Getting started with Azure Bicep [https://zimmergren.net/getting-started-azure-bicep/]. In that post, I also explained how you could automatically convert your JSON ARM templates into Bicep using the Bicep CLI. Regularly, I see new Bicep templates and other code being shared
Deep-linking Azure Log Analytics and Application Insights queries Paid Members Public
For a while, I've wanted to craft deep links (direct links) to queries in Azure Monitor. Either directly to Log Analytics workspaces or to Application Insights resources I have. I have plenty of use cases for this, but most notably is the fact that we want to easily share queries
Enforce authentication when sending Application Insights telemetry Paid Members Public
Microsoft recently announced the capability, and public preview, of authenticated requests to Application Insights. This is an important update for a wide range of reasons. In this post, we'll explore how to configure your Application Insights instance to reject requests that aren't authenticated and with the correct authorization, and also
Create Azure DevOps or GitHub bugs from Azure Monitor logs Paid Members Public
When operating distributed applications it can be a lot of work if you want to copy error details into tickets and work items for your teams to look at. In this post we're taking a quick look at how we can quickly send specific log entries from Application Insights over to Azure DevOps or GitHub.
Excluding failing dependencies from Application Insights logging Paid Members Public
Implement an ITelemetryProcessor to ignore specific dependency failures in your Application Insights service - this help keep the data clean(er), reduces cost, and ultimately reduces false positives.
Querying data from multiple Application Insights instances Paid Members Public
Getting insights into the resources we operate is a crucial part of understanding where we need to improve and what works well. In reality, the insights and telemetry we gather exist in various regions and datacenters. Data sits in multiple subscriptions and different resource groups - even the same application
Upgrade Application Insights to Workspace-based Resource Mode from Classic Paid Members Public
Recently, Microsoft introduced a new option when creating Application Insight instances. A selection to help us choose between the Classic approach, or the modern Workspace-based mode. In the Azure Portal, it can look like this when we create a new Application Insights today: Select the Resource Mode of Application insights
Use Application Insights for Worker Service applications in .NET Core console apps, containers, and any non-HTTP apps Paid Members Public
Relying on Application Insights [https://docs.microsoft.com/en-us/azure/azure-monitor/app/app-insights-overview] to provide great data has always been a core component of anything I create. Recently, I upgraded my projects to .NET Core 3.1 [https://dotnet.microsoft.com/download/dotnet-core/3.1], and in few cases I