Help: Eventstream doesn’t send data to KQL Database after suspending & resuming Microsoft Fabric Capacity
As I mentioned in one of my previous data recipes, I’m currently exploring Fabric RTI. During this learning experience, I’m using my own Fabric capacity, which is an F4. To minimize unnecessary costs, I’m suspending and resuming my capacity at the appropriate moments.
Problem statement
To continue the development of my mobile app, whose core ability is to scan barcodes of consumable articles and send them over for analytics, I’m resuming my capacity, starting to scan barcodes again, sending them to my Eventstream, and finally saving them in my KQL database.
After a couple of minutes, I wanted to validate all the scanned results in my KQL database and navigate to my scanned_barcode table.
As you can see in the screenshot above, my latest entry was from February 13th. At that point, I started to debug to figure out where things were going wrong. So I checked my Eventstream first, navigated to see if any data was coming into the “consumable_processing” node of my topology.
As you can see in the screenshot above, I was getting data in, so the connection between my mobile app and the custom endpoint couldn’t be the issue. This means that I need to continue looking for the issue. Only at that point, I saw what was going wrong, when looking at my destination, you can see that my destination is inactive (as shown in the screenshot below).
Because of this, no data was pushed to my KQL database. By using the “Activate all” button in the menu bar, or by activating the slicer in my destination, I could reactivate my KQL database destination.
Lesson learned
The most important lesson I learned was that Eventstream destinations are not resumed automatically after resuming a Microsoft Fabric capacity.
