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

ColeStuart

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

ColemenWilson

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.

ColemenWilson

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.