A setting that you configure in a Soda Cloud monitor by specifying key:value thresholds which, if exceeded, trigger a notification. See also: notification.
A configuration in a SodaCL check that you use to explicitly specify the conditions that warrant a warn result. See Optional check configurations.
An out-of-the-box metric that you can configure in a checks YAML file. See Metrics and checks.
A test for data quality that you write using the Soda Checks Language (SodaCL). See Metrics and checks.
The file in which you define SodaCL checks. Soda Core uses the input from this file to prepare, then run SQL queries against your data. See How Soda Core works.
The place in Soda Cloud that stores the values of measurements collected over time as Soda Core executes checks.
A column in a dataset in your data source.
The key in the key-value pair that you use to define what qualifies as a missing or valid value in a column. A Soda scan uses the value of a column configuration key to determine if a check should pass, warn, or fail. For example, in
valid format: UUID ,
valid format is a column configuration key and
UUID is the only format of the data in the column that Soda considers valid. See Missing metrics and Validity metrics.
The file in which you configure data source connection details and Soda Cloud connection details. See How Soda Core works.
A storage location that contains a collection of datasets, such as Snowflake, Amazon Athena, or GCP BigQuery.
A representation of a tabular data structure with rows and columns. A dataset can take the form of a table in PostgreSQL or Snowflake, a stream in Kafka, or a DataFrame in a Spark application.
The value for a metric that Soda Core collects during a scan.
A property of the data in your dataset. See Metrics and checks.
The component in Soda Cloud that stores metric measurements. This component facilities the visualization of changes to your data over time.
A set of details you define in Soda Cloud which Soda SQL used when it ran a scan. Sometimes referred to in other systems as a “data quality rule”. Soda Cloud displays Soda Core check results as Monitors.
See Create monitors and alerts.
A setting you configure in a Soda Cloud monitor that defines whom to notify when a data issue triggers an alert. See also: alert.
A command that executes tests to extract information about data in a data source. See Run a scan.
The domain-specific language to define Soda Checks in a checks YAML file. A Soda Check is a test that Soda Core executes when it scans a dataset in your data source. See SodaCL documentation.
A web application that enables you to examine scan results and create monitors and alerts. Create a Soda Cloud account at cloud.soda.io. If you also use Soda Core, you can connect Soda Core to Soda Cloud.
A free, open-source, command-line tool that enables you to use the Soda Checks Language to turn user-defined input into aggregated SQL queries. You can use this as a stand-alone tool to monitor data quality from the command-line, or connect it to a Soda Cloud account to monitor your data using a web application. See Soda Core documentation.
Soda Spark was an extension of Soda SQL that allowed you to run Soda SQL functionality programmatically on a Spark DataFrame. It has been replaced by Soda Core configured to connect with Apache Spark DataFrames. Access legacy documentation.
The value for a metric that Soda checks against during a scan. See Metrics and checks.
In Soda Cloud, the key-value pair that you use to define what qualifies as a missing valid value in a column. A Soda scan uses the value defined in a validity rule to determine if it should pass or fail a check. See also: configuration key.
Last modified on 01-Jul-22
Was this documentation helpful?
Share feedback in the Soda community on Slack.
Help improve our docs!