Has Anyone Set Up Domo Alerts to Identify Long Running Dataflows?

We had an issue this last week where some jobs were duplicating and exploding rows.
Some dataflows ran for 18+ hours without erroring.
I'd like to set up some alerts for this and wondering if anyone has already done something like this and could share their set up.
Thank you
Best Answer
-
The easiest, but perhaps not most efficient, way would be to utilize Domostats datasets, specifically the DataSets report. You can use the Last Run date time field and then a datediff/timediff and set logic in a beastmode that if the time difference between the current time and last updated date/time is beyond a certain threshold to trigger an alert.
If I solved your problem, please select "yes" above
1
Answers
-
The easiest, but perhaps not most efficient, way would be to utilize Domostats datasets, specifically the DataSets report. You can use the Last Run date time field and then a datediff/timediff and set logic in a beastmode that if the time difference between the current time and last updated date/time is beyond a certain threshold to trigger an alert.
If I solved your problem, please select "yes" above
1
Categories
- All Categories
- 2K Product Ideas
- 2K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 308 Workbench
- 7 Cloud Amplifier
- 10 Federated
- 3.8K Transform
- 660 Datasets
- 117 SQL DataFlows
- 2.2K Magic ETL
- 818 Beast Mode
- 3.3K Visualize
- 2.5K Charting
- 84 App Studio
- 46 Variables
- 781 Automate
- 191 Apps
- 483 APIs & Domo Developer
- 84 Workflows
- 23 Code Engine
- 43 AI and Machine Learning
- 22 AI Chat
- 3 AI Projects and Models
- 18 Jupyter Workspaces
- 408 Distribute
- 116 Domo Everywhere
- 281 Scheduled Reports
- 11 Software Integrations
- 146 Manage
- 142 Governance & Security
- 8 Domo Community Gallery
- 49 Product Releases
- 13 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 115 Community Announcements
- 4.8K Archive