When directly scheduling a Microsoft Fabric notebook we are able to see previous runs, the Monitor tab also shows us a history of runs that have occured across the workspaces. I want to know if I'm able to get this data from an API as I want to be able to setup notifications if a particular notebook had failed at some point and even look at providing details from the item snapshot to have some context without having to look at the platform. I'm aware you can schedule Data Pipelines and send an email on failure but this seems like a laborious task if I have to go through each Pipeline and add this in rather than having a table I can use as a log.
3 Comments
- Banafshe_AnarakNew Member
Agreed! It would be very helpful if we could set up email notifications for notebook failures like we do for PBI semantic models.
- abauman1New Member
In addition to the API, I would ask that we have the same failure notification functionality that we would have with pipelines (on success email, on failure email, retries, etc...).
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Exported PDF from PowerBI to not have any indents/borders
Currently, using the "Export to PDF" option in PowerBI results in two consistently buggy results: A white border/indent is generated, increasing the size of the page from 8.5x11 to 9x11.5 Sometime...EliShalev40 minutes agoNew MemberNew1View0likes0CommentsAdding a Container for Logical Grouping of Activities in Data Pipelines
Dear Team, I would like to propose a feature enhancement for Data Pipelines in Microsoft Fabric that allows the logical grouping of activities into a container. This container would serve to: Im...lukas_karlovsky1 hour agoNew MemberPlanned868Views15likes5CommentsSupport Native SQL LIKE / NOT LIKE Wildcard Filtering Across Power BI Reports
Description Currently, Power BI does not provide a native way for report consumers to perform dynamic SQL-style wildcard filtering using patterns such as LIKE '____' - Above return all values wit...Seeralan3 hours agoNew MemberNew4Views0likes0Comments