Dataset Watchdog Logs

ssf24
ssf24 Member
in Governance & Security

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

  • ArborRose
    ArborRose Coach

    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! **

  • ssf24
    ssf24 Member

    Thanks for putting this response together. A couple updates and then my responses:

    Over the last 3 days, the Watchdog job has run in the 8am, 9am, and 10am hours only. No idea why those hours but that's what I'm seeing.

    1. We run DomoStats and our History dataset has close to 62 million rows dating back to 2018 so we have not encountered these limits. Granted, Watchdog may be configured differently, but the current log is only at 2200 rows so I doubt that's large enough to come up on any limits.

    2. This is interesting and I've tested against this. I added a row to the config file designed to fail or trigger essentially checking against a dataset updating every minute, which it doesn't. This was to see if a failed or triggered entry would update the log. While Watchdog continues to say it runs every hour, it neither updates the log nor does it email an error notification.

    3. I'm aware of the 100 row limitation. Currently, I'm at 19 rows on my config file.

    All in all, I need to understand specifics of the limitations of DataSet Watchdog. I understand I'm trying to repurpose it for a broader and perhaps unintended use case, but all documentation suggests it runs and logs every hour and that's it. If that's is not the case, then I need to know the specific limits so I can work around this. If the developers did not want this dataset to run in perpetuity due to the potential of unlimited geometric growth, that's understandable but there must be a know boundary that's just not published.

Categories