Dataset Watchdog Logs

I'm starting to use dataset watchdog and I'm finding most of it pretty intuitive. I created a config file and started a watchdog job a few days ago and now the execution log is not updating. Are there limits to the log as it exists?

Tagged:

Answers

  • If your execution log is no longer updating, there are a couple of possible reasons:

    1. Log Retention or Display Limits

    Domo doesn't appear to have officially published a specific size or time-based limit on Watchdog execution logs, but people have commented that:

    • Logs may stop displaying updates after a certain volume of entries.
    • Logs might not persist indefinitely, especially if the job has been running for several days without new triggers or events.

    This behavior is consistent with other Domo logging tools like DomoStats, which I believe has a 30-day limit on activity log retention.

    2. Watchdog Job Issues

    Check whether:

    • The Watchdog job is still running.
    • The config dataset hasn’t been modified or dropped.
    • The underlying datasets being monitored are still updating—Watchdog only logs activity when its conditions are triggered (e.g., thresholds crossed or failures detected).

    3. Config Dataset Limits

    Keep in mind the config dataset is limited to 100 rows, which might impact behavior if you’re trying to track many datasets or dataflows.

    You could try stopping and restarting the job. But there may be a back-end glitch that would lead to contacting Domo Support for assistance.

    ** Was this post helpful? Click Agree or Like below. **
    ** Did this solve your problem? Accept it as a solution! **