Automation and collection
Metric monitors
Select a value, set a time range and trigger condition, and get notified automatically when it is met.
A metric monitor checks one value regularly, such as “order count in the last hour”, and notifies you by email or Feishu when a condition is met (for example, below 100). It does not produce analysis reports; for regular reports, use scheduled tasks.
Metric monitors are in Beta. Only explainable SQL aggregate metrics (such as sums and counts) are supported, not numbers that depend on Python or other extra calculations.
Entry: main navigation on the left → “Automation”, or create directly from a data table in a conversation or dashboard.
Create a monitor
Select a value
In a data table in a conversation or dashboard, select the value to monitor and click “Monitor this metric”.
Confirm the scope and calculation rule
The system explains the value's subject, business filters, and calculation rule; check that they match your definition. If it cannot fully explain them, clarify the metric and time range in the conversation and create the monitor again.
Choose a time range
| Method | Description |
|---|---|
| Rolling window | Last 1 hour, last 24 hours, last 7 days, or a custom number of minutes; recalculated on every check |
| Calendar period | Today up to this check, yesterday, this week, last week, this month, last month |
| Text description | For example “past three hours” or “since the start of this week”; confirm the recognized result |
| Keep the original query's range | Fixed dates in the original query do not move; suitable only for watching the same period |
If the time field has dates only, hour or minute windows cannot be used; choose calendar days. In “Advanced settings”, you can set the time zone of the data and the minutes to wait for data to arrive.
Set the trigger condition
Choose a condition: greater than, less than, equal to, greater than or equal to, less than or equal to, not equal to, within range, or outside range, and enter the threshold.
Choose an Action and test
Choose an email or Feishu Action, and click “Test current definition” to see the current value. After changing conditions, test again; test results are valid for 15 minutes.
Create and enable
Click “Confirm rule and create monitor”. By default it checks every 10 minutes, and notifications are at least 60 minutes apart. Monitors are disabled after creation; enable them once confirmed.
Notification rules
- A notification is sent the first time the condition is met.
- During the cooldown, no repeat notifications are sent; if the condition is still met when the cooldown ends, another notification is sent.
- After recovering, meeting the condition again triggers a new notification.
Make good use of it
- Monitor aggregates, not rankings. “East China sales” is a stable metric; “the store with the highest sales” changes and is not suitable. When the query has Top N or pagination, the target row may drop out of the result, which counts as a failed check, not 0.
- Set a wait time when data arrives late. If data is loaded hourly, set the minutes to wait for data so incomplete data is not mistaken for a drop.
- Leave headroom in thresholds. Set thresholds based on historical fluctuation and adjust the cooldown to avoid frequent alerts.
Monitor problems
| Status | Cause | Action |
|---|---|---|
| Needs repair; monitor paused | Fields in the data source changed | Fix the data source, test again, save, and enable manually; or query again and create a new monitor |
| Retrying | Checks failed consecutively and are still retried at the original frequency | Check the data source connection; the last successful value does not reflect current data |
| Monitor disabled | The last check failed | Fix the problem and enable again |
| Failure alert not delivered | The Action is misconfigured | Check the Action |
File data sources reflect only synced data; monitors do not fetch external files automatically. The confirmation dialog before deactivating a member warns that their monitors will pause.
Common issues
| Symptom | Cause | Action |
|---|---|---|
| “Cannot confirm this metric right now” | The original query's metric or time range is unclear | Clarify the metric and time range in the conversation and retry |
| No replaceable time range recognized | The query has several time fields or complex time conditions | Keep a single time condition in the conversation and query again |
| Test fails | The metric is not a number, or the business row is not unique | Use a single aggregate value |
| No Action to choose | There is no Action yet | Click “Manage Actions” to create one |