Link Search Menu Expand Document

Soda Cloud architecture


Soda Cloud uses Soda SQL in the background to help you monitor your data and alert you when there is a data quality issue.

In Soda Cloud, you connect your account to your data source and define a schedule for scans of your data. To actually execute the scan, Soda Cloud connects to a hosted Soda SQL instance via a secure API and Soda SQL runs the scan. When it completes a scan, it pushes the results to your Soda Cloud account where you can log in and examine the details in the web application. Notably, Soda SQL pushes metadata to Soda Cloud; by default all your data (barring any sample data you explicity instruct Soda SQL to send to Soda Cloud) stays inside your private network. See Data security and privacy

When you create a monitor in Soda Cloud’s web application, Soda SQL uses the monitor settings to add new tests when it runs a scan on data in a specific warehouse. A monitor is essentially a way to create Soda SQL tests using the web application instead of adjusting scan YAML file contents directly in your Soda project directory.

You can use monitors to automatically detect anomalies, view samples of data that failed a test, and track data quality over time. Soda Cloud stores your scan results and prepares charts that represent the volume of failed tests in each scan. These visualizations of your scan results enable you to see where your data quality is improving or deteriorating over time.

Follow the Soda Cloud Onboarding path to start monitoring your data.


Go further

Last modified on 18-Oct-21

Was this documentation helpful?
Give us your feedback in the #soda-docs channel in the Soda community on Slack or open an issue in GitHub.