Validio 6.0: Custom priority settings and intuitive errors and warnings

TL;DR

The Validio 6.0 release focuses on making data quality and incident management more precise and actionable, with updates to prioritization and error handling.

We’ll dive into the core updates in this blog post. For the full update of news and fixes, check out the changelog.

User-defined priority

You know that one data asset that doesn’t look like much for the world, but it’s what’s feeding management reports? We know that you know your data best, and with the 6.0 release, you can set custom priority on Sources and Validators. Bronze source that feeds the Gold layer? Set the priority to High. Low stake pipeline? Priority set to low. Incident groups inherit the priority, so queues and on-call channels reflect business impact.

This helps:

• Route incidents to the right owners with the right urgency
• Keep Tier 0 assets like dashboards or compliance reports front and center
• De-prioritize low stakes pipelines to reduce noise

How to use it

• Set priority during configuration or from the list of Sources or Validators
• Combine it with Ownership assignment to make sure relevant issues are prioritized

Intuitive errors and warnings, right where you need them

Errors are now shown where they happen. Instead of scanning a global list, you’ll see errors directly on the affected tabs of a Source’s details page: Validators, Schema, Filters, Windows, Segmentations, plus clearer messages on the resource itself.

Why it matters:

• Quicker and easier solution of issues, whether there’s a formatting issues or missing credentials, you know where the issue happens and what the issue is
• Easier see schema changes propagated to downstream resources to see impact of updates

In addition to these updates, we’ve also made several updates including increasing sensitivity for dynamic thresholds and added support for multiple SAML auth backends. See the changelog in the documentation for all details.