Skip to content

Commit f54b39f

Browse files
committed
Remove observer docs
1 parent e403fdc commit f54b39f

23 files changed

+1
-213
lines changed

docs/cloud/features/alerts_notifications.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,6 @@ Tobiko Cloud sends an alert based on a *trigger*. There are two types of trigger
3232

3333
Events are tied to steps in the SQLMesh `plan` and `run` processes. For example, you could alert whenever a `plan` succeeded or a `run` failed.
3434

35-
Measures are [automatically calculated](../../guides/observer.md#measures) at run time.
36-
3735
Choose whether the alert will be triggered by a Measure or Event in the alert's Trigger Type field.
3836

3937
![Image showing the add Alert page trigger type field](./alerts_notifications/add_alert_trigger_type.png)
@@ -63,7 +61,7 @@ Finally, choose a Notification Target where the alert should be sent (described
6361

6462
### Measure triggers
6563

66-
Tobiko Cloud Alerts can be triggered when a [measure](../../guides/observer.md#measures) exceeds a threshold or meets a condition.
64+
Tobiko Cloud Alerts can be triggered when a measure exceeds a threshold or meets a condition.
6765

6866
To configure a measure alert, first build the condition that triggers the measure. Choose the measure of interest, the comparison operator, and a threshold value.
6967

docs/guides/observer.md

Lines changed: 0 additions & 209 deletions
This file was deleted.
-36.8 KB
Binary file not shown.
-32.1 KB
Binary file not shown.
-63.3 KB
Binary file not shown.
-11 KB
Binary file not shown.
-147 KB
Binary file not shown.
-164 KB
Binary file not shown.
-133 KB
Binary file not shown.
-139 KB
Binary file not shown.

0 commit comments

Comments
 (0)