- \n
- Enabling real-time performance optimization, fault detection, and prevention.<\/li>\n
- Ensuring scalability.<\/li>\n
- Enhancing security.<\/li>\n
- Aiding in cost management.<\/li>\n
- Improving the user experience.<\/li>\n<\/ul>\n
Additionally, monitoring supports compliance, predictive maintenance, and continuous improvement, making it an essential practice for maintaining a robust and efficient analytics ecosystem.<\/p>\n
By integrating technologies like Data Factory<\/a>, Synapse Data Engineering<\/a>, Synapse Data Science, Synapse Data Warehousing, Synapse Real-Time Analytics, Power BI, and Data Activator into Microsoft Fabric<\/a>, it now facilitates the end-to-end analytical solution. With more power and features it becomes a challenge for administrators to manage these resources under Fabric. However, Fabric provides tools to tackle these challenges.<\/p>\n
Monitoring In Microsoft Fabric<\/h2>\n
Undoubtedly, Microsoft<\/a> understands the critical need for monitoring resources, so Fabric provides a full set of features to monitor and track the use of resources and activities.<\/p>\n
Monitoring Hub<\/h3>\n
As the name indicates, Monitoring Hub helps users monitor activities within Microsoft Fabric.<\/strong> It is a station to view and track active activities across Microsoft Fabric, such as dataset refreshes, Spark Job runs, and many others, from a central location.<\/p>\n
A user with read permissions on datasets of any of these items could see them in their Monitoring Hub.<\/p>\n
Monitoring Hub displays activities based on which service is being used when Monitoring Hub is selected. During the Microsoft Fabric public preview, Monitoring Hub was available for Power BI<\/a>, Data Factory, Data Engineering, and Data Science workloads only. Now that Fabric is generally available (GA), watch this space as the monitored offerings are likely to expand.<\/p>\n
Monitoring Hub displays the standard information below within columns across all workloads:<\/p>\n
- \n
- Activity name<\/strong>: Name of the artifact.<\/li>\n
- Status<\/strong>: Cancelled, Completed, Failed, In Progress, Not Started and Unknown.<\/li>\n
- Item type<\/strong>: To which type it belongs like Dataset, Datamart, Lakehouse, Data pipeline, Spark Job Definition, and more.<\/li>\n
- Start time<\/strong>: At what time its execution starts.<\/li>\n
- Submitter<\/strong>: Who initiates the activity?<\/li>\n
- Location<\/strong>: To which workspace it belongs.<\/li>\n
- Duration<\/strong>: How much it took to process.<\/li>\n<\/ul>\n
![\"Screenshot](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2023\/11\/Monitoring-Hub-Screen-shot.jpg\")
<\/a><\/p>\nApart from these, it provides additional column options specific to the viewing context, such as Power BI or other workloads.<\/p>\n
Not only that, but the user could also further open a detail pane for the item itself when you hover over the item.<\/p>\n
![\"Screenshot](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2023\/11\/MicrosoftTeams-image-14-1024x451.jpg\")
<\/a><\/p>\nTrack User Activities in Microsoft Fabric<\/h3>\n
Monitoring activities is one part of what an administrator needs to do, but to monitor who is taking what action on which item of Fabric is a crucial piece of information that helps an organization regulate compliance and record management.<\/p>\n
Microsoft Fabric logs activities in the Power BI activity log and in the unified audit log.<\/strong> These log features were there before Fabric\u2019s debut and existed only for Power BI. In light of that, for Power BI there are a lot of operations that have been tracked. But for other Fabric workloads, currently only create, read, update, and delete operations can be tracked.<\/p>\n
Microsoft recommends using the Power BI activity log as it contains information related to Fabric auditing events only. Also, Power Platform administrators and Power BI administrators can access these, so global administrator roles aren\u2019t required to access them.<\/p>\n
Within the Power BI activity log, the complexity comes in retrieving the logs. Administrative users need to be familiar with the Power BI Admin API and Power BI PowerShell modules as well as understand there can be a lag of 30 to 60 minutes to retrieve event information.<\/p>\n
On the other hand, if one opts for the Audit Log, you will need to be a global admin, a role that most organizations are not comfortable granting to very many people. If one has audit access only then they can access logs using Microsoft Purview.<\/p>\n
With Fabric, one of the essential governing tools is Microsoft Purview<\/a>. This tool is likely to be further integrated in the future, and once it is live, most organizations are likely to go with Audit Logs.<\/strong> With that choice, the user will not only use PowerShell to access the information from logs, but they will also have the option to use the GUI to search, filter and retrieve information in CSV format.<\/p>\n
Feature Usage and Adoption Report<\/h3>\n
As Microsoft rolled out Fabric, it introduced a new Fabric admin role. This role is responsible for the management of the organization-wide settings that control how Microsoft Fabric works. Users assigned to admin roles configure, monitor, and provision organizational resources.<\/p>\n
Below is a snapshot of the admin roles and their duties.<\/p>\n
![\"Admin](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2023\/11\/MicrosoftTeams-image-16-1024x326.jpg\")
<\/a><\/p>\nWith a minimum role of Fabric admin, the Admin Monitoring workspace is enabled for the user, as shown in the below snapshot:<\/p>\n
![\"Screenshot](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2023\/11\/MicrosoftTeams-image-15.png\")
<\/a><\/p>\nIt is automatically installed during the first time any Microsoft Fabric admin accesses it.<\/p>\n
In this workspace, a report called \u201cFeature Usage and Adoption report\u201d is available, which provides a comprehensive analysis of the use and adoption of different features in your Microsoft Fabric tenant.<\/strong><\/p>\n
![\"Screenshot](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2023\/11\/Power-BI-Admin-Monitoring.jpg\")
<\/a><\/p>\nThis report consists of three report pages:<\/p>\n
- \n
- Activity Overview<\/strong>: Provides a summarized view of activities and usage across the entire organization. Examples include daily activities, user trends, most active capacities, and workspaces. One can also view the activities of the entire organization (by user level as well).<\/li>\n<\/ul>\n
- \n
- Analysis<\/strong>: Visualizes data across multiple activity dimensions. It provides a daily count of activities and users by date and a decomposition tree that automatically aggregates data and enables drilling down into dimensions in any order. It helps to understand the activities according to operation and user.<\/li>\n<\/ul>\n
- \n
- Activity Details<\/strong>: Displays detailed information on specific or multiple capacity or workspace activities. Detailed information is available via drill through from Activity Overview or Analysis pages.<\/li>\n<\/ul>\n
- Analysis<\/strong>: Visualizes data across multiple activity dimensions. It provides a daily count of activities and users by date and a decomposition tree that automatically aggregates data and enables drilling down into dimensions in any order. It helps to understand the activities according to operation and user.<\/li>\n<\/ul>\n
- Status<\/strong>: Cancelled, Completed, Failed, In Progress, Not Started and Unknown.<\/li>\n
- Activity name<\/strong>: Name of the artifact.<\/li>\n
![\"Microsoft](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2023\/11\/MicrosoftTeams-image-13-1024x147.jpg\")
<\/a><\/p>\n![\"Microsoft](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2023\/11\/MicrosoftTeams-image-10-1024x312.jpg\")
<\/a><\/p>\n