One of the big issues with developing Power Automate Solutions is determining how to monitor power flow runs and power automate applications.
It all starts with an idea generation form that allows the business to register its automation idea. Whether the automation is done via an automation developer or a citizen developer an ID is generated that is emailed to the author of the idea.
For all Power Applications that are developed using the ID received, a patch function is added to the onStart property that adds who ran the app, Date Time, App ID to a SharePoint list.
For all Power Flow runs that are developed using the ID received a SharePoint create item action is configured that writes the ID, Date Time, Run Time, Platform, and Result. (# of Success, # or Errors if processing records)
The reason to write it to SharePoint is to limit premium license needs, if we write directly to SQL it will require a premium license for each flow and application which greatly increases the license cost.
A scheduled flow is to be run daily that takes all list data and writes it to SQL and removes the data as it writes it to SQL. This requires only one premium license to write the list to SQL. This flow would also remove the list data that has been written to SQL
The cherry on top of this whole basic solution is to write a Power BI report that shows the stats for each idea that was entered. If you add ROI metrics you can now get a basic cost savings based on the usage monitoring that is being written to SQL.
While this is very basic I have found it as a very simple place to start when having the how do we monitor our usage of Power Platform applications.
コメント