In this post I share some tips for implementing FUAM in Microsoft Fabric. Since I have seen multiple questions relating to FUAM appear online.
To clarify, FUAM stands for Fabric Unified Admin Monitoring and is a popular monitoring solution that has been developed by two Microsoft employees.
You deploy FUAM in a Fabric workspace. So that it can extract metrics which can be used for a holistic monitoring view. Typically through a central Power BI report like the one shown below.
Even though it is not an official Microsoft product FUAM is a popular solution accelerator. Like other items covered in a previous post FUAM caused some excitement during FabCon. Plus, FUAM is listed in the Fabric Toolbox.
After seeing multiple questions about FUAM online I decided to share some tips I put together. Along the way I share plenty of links.
Tips for implementing FUAM in Microsoft Fabric
In reality, the due responsible for FUAM did a great job documenting how to deploy FUAM. However, I want to highlight some key points in this post. To help others avoid common issues. Plus one tip to make your workspace stand out more. So let’s begin.
Install Capacity Metrics App fully before deploying FUAM
One very common issue I see from others is that they get an error about unable to find metadata for a particular table when they run the orchestration pipeline.
This is typically due to the fact that they did not complete the full process to install the Capacity Metrics App. You need to make sure you follow all the steps and run the app at least once before you start the pipeline.
Notebook run time
You may encounter a rare occurrence where it takes a while for the Deploy_FUAM notebook to complete. Either as part of the initial the deployment or after downloading an updated version of the notebook.
If this occurs it is probably due to external reasons such as other events happening in the same capacity. My advice is to wait patiently for the notebook to complete.
Add users to the connections in Microsoft Fabric
If you intend for others to update FUAM in the future make sure you add users to the created connections appropriately. So that they can see the connections before they start the notebook.
You can do this in Microsoft Fabric by going into ‘Manage connections and gateways’.
Configuring the main FUAM orchestration Pipeline
In reality there are three key points I want to highlight about configuring the main orchestration pipeline.
First point is to make sure you change the activity_days_in_scope value. By default, the value is set to 30 even though its range is between 2 and 28.
Second point is relating to the optional keyvault parameters.
If whoever initially runs the pipeline is not a Fabric admin then you need to make sure you add the relevant values to secrets in an existing Azure Key Vault and then reference them in the parameters section. Otherwise the pipeline will likely fail.
Third point is relating to when you intend to perform an update. Make sure you follow the advice given in the update FUAM instructions. Especially the advice to take a screenshot of your current pipeline parameters. Because they tend to reset after an update.
Recommended FUAM logo
My last tip is one to make your implementation of FUAM stand out. Which is to add the workspace logo when you create the FUAM workspace.
Adding the logo makes a big difference visually when working with FUAM within Microsoft Fabric.
Final words about tips for implementing FUAM in Microsoft Fabric
I hope these tips for implementing FUAM in Microsoft Fabric helps some of you. Because FUAM has a lot to offer compared to alternative solutions.
Of course, if you have any comments or queries about this post feel free to reach out to me.
Be First to Comment