Data-driven alerts notify users when data meets conditions (e.g., sales > $10K). Let’s examine when Tableau checks these:
Alert Mechanics:
Enabled per site (Settings > General > Data-Driven Alerts).
Backgrounder evaluates conditions against extract data.
Check Intervals: Configurable via tsm configuration set -k dataAlerts.checkIntervalInMinutes (default: 60 minutes).
Refresh Trigger: Also checks post-extract refresh for immediate updates.
Option A (Every 60 minutes): Correct.
Details: Default interval—Backgrounder polls every hour to evaluate alert conditions.
Config: Adjustable (e.g., -v 30 for 30 minutes).
Option D (Whenever extracts in the related workbook are refreshed): Correct.
Details: An extract refresh updates the data, triggering an immediate alert check to catch changes promptly.
Why: Ensures timely notifications without waiting for the next poll.
Option B (Every 10 minutes): Incorrect.
Why: Not the default—possible via config, but not standard.
Option C (Whenever a new extract is published): Incorrect.
Why: Publishing creates the extract; alerts trigger on refreshes or polling, not initial publication.
Why This Matters: Timing affects alert responsiveness—balancing frequency and server load is key.
[Reference: Tableau Server Documentation - "Data-Driven Alerts" (https://help.tableau.com/current/server/en-us/data_alerts.htm)., , ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit