<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AppInsights on AdaTheDev Blog</title><link>https://www.adathedev.co.uk/tags/appinsights/</link><description>Recent content in AppInsights on AdaTheDev Blog</description><generator>Hugo -- gohugo.io</generator><managingEditor>adathedev@gmail.com (Adrian Hills)</managingEditor><webMaster>adathedev@gmail.com (Adrian Hills)</webMaster><lastBuildDate>Fri, 17 Dec 2021 13:02:00 +0000</lastBuildDate><atom:link href="https://www.adathedev.co.uk/tags/appinsights/index.xml" rel="self" type="application/rss+xml"/><item><title>Troubleshooting Azure Function Consumption Plan Scaling</title><link>https://www.adathedev.co.uk/2021/12/troubleshooting-azure-function.html</link><pubDate>Fri, 17 Dec 2021 13:02:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2021/12/troubleshooting-azure-function.html</guid><description>I recently encountered an issue with an Azure Function Event Hub trigger running on a Linux Consumption Plan, whereby events stopped being consumed by the trigger once it went to sleep. I learned a lot about consumption plan scaling and diagnosing what was going on, so in this post I&amp;rsquo;m going to share the key takeaways that I picked up as it was a bit of a journey.
Background: Azure Function Event Hub trigger stopped processing events This was in a low-throughput scenario for testing - so the rate of events coming into the Event Hub was low/sporadic.</description></item></channel></rss>