From the course: Data Quality Testing with Great Expectations

Unlock this course with a free trial

Join today to access over 25,500 courses taught by industry experts.

Triggering actions with checkpoints

Triggering actions with checkpoints - Great Expectations Tutorial

From the course: Data Quality Testing with Great Expectations

Start my 1-month free trial Buy for my team

Triggering actions with checkpoints

“

Now that we know how to create expectations and use them to run validations in GX, let's look into what to do with those validation results. Detecting errors in our data with failed validations is only half of the work. Once an error is found, we need to send some alerts and then actually fix the problems. In GX, the first two steps in this lifecycle are covered by checkpoints. A checkpoint is a bundle of a set of validation definitions and actions that are taken based on the results of those validations. A common example for an action is sending a Slack message when a validation fails. Checkpoints are one of the really nice convenience features of GX. Instead of having to read out the test results and then implement the actions yourself, they already come built-in. GX offers several built-in actions including sending an e-mail, sending a Slack or or Microsoft Teams message and updating data docs. You can also configure custom actions, but let's just start with a built-in one for now.…

Contents