Diffing data

Being able to quickly and accurately track changes in your data is enormously helpful when it comes to debugging issues. Zeno ships with two separate strategies for using the differences between data states to diagnose data issues.

1. Diffing arbitrary data states
2. Tracking historical differences

Zeno can help identify issues and verify functionality during releases. When releasing new functionality, it is helpful to perform a “diff” between a data state produced with the current release, and a data state produced with the candidate release. Expected changes should be visible in this report, and unexpected side effects of changes will be highlighted in the report. With this report, We can get a bird’s eye view of the differences broken down by type, drill down into the differences broken down by field, and even zoom in to inspect individual object instances which are different where we expected them to be the same. See diffing arbitrary data states to learn how to do this.

Zeno can also help identify issues that might crop up over time in your data set. Being able to go back over some trailing number of versions and quickly pinpoint changes that happened, and when those changes occurred, for a specific object can help pinpoint the issue when something went wrong. See tracking historical differences to learn about Zeno’s facility for tracking historical changes.