DataKitchen Documentation

DataOps Automation Help

DataOps Observability Help

DataOps TestGen Help

DataOps Concepts

Explore Tutorials

Resources

DataKitchen home open_in_new

The DataOps Cookbook open_in_new

Recipes for DataOps success open_in_new

DataKitchen webinars open_in_new

The Data Journey Manifesto open_in_new

The DataOps Manifesto open_in_new

Automation release notes

Observability release notes

TestGen release notes

Frequently asked questions

DataKitchen supports the three most recent major versions of Google Chrome, Mozilla Firefox, and Microsoft Edge for its software. For more information, see Browser Support.

DataOps TestGen includes 40 types of tests that verify the health of your data. Learn more about each test in the Test Types documentation.

You can schedule orders to run at regular intervals using a form in the Automation UI or via the command line. For advanced scheduling, it's also helpful to understand cron expressions.

A journey represents a collection of components in your data estate that are responsible for creating a data analytic deliverable. The components that make up a data journey are often loosely related, spread across different tools, and can be managed by different teams. Observability lets you create a holistic, end-to-end view of the components and relationships that make up a journey in your data estate.

You can connect supported input/output components as data sources and data sinks. See Supported Connectors for the official list. All other tool connections can be accomplished using container nodes and storing tool credentials as secrets.

Observability provides end-to-end visibility across the tools and assets in your data estate by collecting events from your environment, comparing this information against expectations, displaying the results, creating alerts, and sending notifications. See Introduction to Observability for more information.

DataOps TestGen provides support for Redshift and Snowflake databases.

Observability receives, aggregates, and displays event information published by a customer's tools and data assets (i.e. components). The system does so by exposing a REST API, where the events are received and ingested in real time through an Observability agent or by sending events to the Event Ingestion API directly. See the Integration Guides for more information.