Adventures with App Insights: Tracking Custom Events in .NET Core Function Application

WARNING: According to this article, https://docs.microsoft.com/en-us/azure/azure-functions/functions-dotnet-dependency-injection#logging-services, is NOT A RECOMMENDED PRACTICE. While what I have done works, according to the article, adding AddApplicationInsightsTelemetry() to the services collection “registers services that conflict with services provided by the environment.” In a previous article, we looked at how to track custom events in Azure Application Insights from a .NET Core Web…

Adventures with Azure: Cosmos DB, Azure Functions, Event Grid, Oh My!

To get a better understanding of the Cosmos DB Change, Event Grid, retry and fail over logic, I decided to build a system that would respond to changes in a Cosmos DB, send events to an Azure Event Grid, which in turn would forward the events to subscribers. I broke this article in to three…

Adventures with Azure DevOps: Create a Custom Dashboard Widget

I have been doing a lot with Azure DevOps lately, from building pipelines to dashboard. As I was building out a dashboard with various widget, I wondered if it was possible to create a custom dashboard widget! What do you know? You can! The widget are a combination of HTML, JavaScript and CSS. So I…

Adventures with Logic Apps: Working with @Outputs

In a previous article, Logic Apps Calling Logic Apps, I show how to have a parent Logic App call child Logic Apps. Now I want to have my child Logic App return a value that my parent Logic App can do something with. This article assumes you are familiar with Logic Apps. Getting started We…

Adventures with Logic Apps: Logic Apps Calling Logic Apps

There are several articles available on how Logic Apps can call other Logic Apps. Most of the examples I found were larger in scope or overly complicated, geared towards specific business cases. I wanted a simple example, but one that was robust enough that would lead to great learning experience. So let’s get started. Create…

Adventures with Cosmos: Alerting and 429 Status Codes

During periods of peak transactions Cosmos may return a 429 Status Code – Too Many Requests, which means the collection has exceeded the provisioned throughput limit (RUs) and that you should retry the request after the server specified retry after duration. I want to setup alerting on both an Azure Function and the underlying Cosmos…