Sifflet

Stable

With Data quality (Enterprise), Sifflet rule runs and asset health come in, failures open Nistor incidents, and Sifflet rules can migrate to Nistor checks.

CollectsChecks (Data quality)Health (Data quality)

Works through Nistor Enterprise: Data quality

Keep the data-quality monitoring you already have, and see it on the same graph as your lineage and runs. Sifflet connects through the Data quality plugin of Nistor Enterprise.

What Nistor collects

With Data quality (Enterprise):

  • Checks: every Sifflet rule run, with its result.
  • Health of each monitored asset; failures open Nistor incidents with their blast radius.

On Open Source alone, the connector holds the connection and can test it, but brings nothing in.

Migrate and write back

Teams moving off Sifflet can migrate its rules to Data quality checks. Nistor's rules do not trigger Sifflet checks.

Nistor can also write a verdict back to Sifflet. This is off by default, and it uses a separate Sifflet token with the Editor role.

Set it up

Install the Data quality plugin, create a Sifflet API token with read access, then add the connection in Nistor. The README in the repository lists the scopes.

The setup guide comes with the docs, soon.