Skip to main content

Alert Trigger Time Detailed Explanation

Alerts can be divided into card alerts and dataset alerts. This article will explain the logic of alert trigger time as "after data update" from these two types of alerts, and whether real-time alert triggering can be achieved.

image.png

I. Card Alert Quasi-real-time Trigger Logic

  1. Data source is direct connection dataset

  2. Real-time card no-cache setting is enabled

    image.png

  3. Enable URL Trigger

  4. Through other external systems or BI server's scheduled task function, request the URL at fixed times as needed

II. Dataset Alert Indirect Quasi-real-time Trigger Solution

  1. Dataset alerts theoretically don't have real-time triggering:

Dataset alert triggering after data update refers to the dataset's own update, not card data updates, nor database data updates. So generally, from a product functionality perspective, dataset alerts cannot achieve real-time triggering effects

  1. Solutions:

Solution 1: Enable URL trigger, write a script to trigger dataset updates, combine usage to achieve quasi-real-time dataset alert triggering:

image.png

Solution 2 (not recommended usage): Relax direct connection dataset update frequency, such as updating datasets every 1 minute. At this time, resource pressure is mainly on the database itself. This needs to be evaluated based on the dataset size, update time required, database efficiency, and BI platform resource conditions to determine if this solution is suitable. Currently no customers use this solution.

Others:

Card alert and dataset alert usage reference: Alert Product Description