Versions Explorer

Change Log

An automatically generated diff for event schemas

With the Version Change Log, you'll get overview for version-to-version changes in your event structures.

Have noisy properties that change often? No problem - they'll filter out automatically.

When you use semantic versioning, you'll also be able to compare prerelease builds to automatically catch when unintended or unwanted changes occur. No more CASE statements to deal with accidental changes.

Change Details

Dig into changes across versions

With the detailed changes view, you can view a detailed diff across any two versions of your events.

Changes Tracked Include:

Cardinality Changes

A drastic cardinality change could indicate that an expected value is no longer fitting its definition, or a variable has been replaced with a constant. We minimize noise here with an intelligent rules engine.

Type Changes

Nothing can break a data pipeline faster than a string sneaking its way into a numeric property. Don’t let that get to production!

% of Events

If a property disappears from a payload, you may have some funky data down the line. Similarly, if an “occasional” property, like ERROR_MSG starts to appear more frequently, you probably want to know.

% Null / Empty

We’ll let you know if the percentage of values NULL (or EMPTY array) changes.

What Are You Waiting For? Start Your Free Trial Today

Level up your Data Stack.

Get Started
Frequently Asked Questions
How do I define an "event"?

You can define an event by providing up to 3 properties that go into an event definition. Read more in the docs

If I accidentally send PII, can it be removed from AutoDocs samples?

Yes! Security and privacy is of the upmost importance. Review the docs on how to do this.

Are there limits to the number of events or versions?

There are. In order to safegaurd the system (for example, if you define a user_id field as an event descriptor) - any config that has more than 250 unique events or 200 unique versions will be disabled. These are flexible limits, if you have a need for more events/versions, please contact us.

How deeply nested does AutoDocs scan?

By default, events will be explored up to 10 levels deep, including nested arrays. This is a flexible limit, please contact us if you need this limit increased.

© Data Stuff, LLC Privacy Policy Terms of Service Acceptable Use