Web API Stream to Alert
Create a web data stream, sync it into Rokks, and add an alert that watches the resulting data.
- Open Web Data and create a connection.
- Add a stream for one endpoint.
- Test a sample response.
- Review the generated transform plan.
- Configure a sync schedule.
- Wait for Dispatcher to submit the first scheduled sync, then confirm in the Job Queue that it finishes successfully.
- Build a small dashboard widget from the stream.
- In the Widget Builder, create and run a continuous-analytics rule that emits the signal you want to monitor.
- Open Workspaces → Attention, choose Manage rules, then choose Add rule. This action remains unavailable until at least one continuous signal exists.
- Select the existing signal, configure its condition, threshold, duration, cooldown, severity, and delivery channels, then choose Save. The alert editor has no test action.
Manual Web API Sync and Full Sync actions are currently unavailable in the UI and Sidekick. This tutorial therefore uses the first Dispatcher-scheduled run as the end-to-end validation.
Common mistakes
Section titled “Common mistakes”Do not build the widget or alert before the first scheduled sync has completed and its output has been validated.
Do not try to create an alert directly from a source field. Alert Rules watch existing continuous-analytics signals; create and run the signal first.
If the alert does not trigger, check the stream job first. A rule can be correct while the source data is stale, empty, or loaded into a different tenant than the one you are testing.