Expectations and Conditions

In DataOps Observability, the events received, components generated, journeys built, and instances captured let you see your data estate as it is. You can configure expectations, conditions, and rules to establish how your data estate should be.

Component expectations

You know when events should happen in your tools and assets. Observability allows you to set schedule expectations on your batch pipelines and arrival window expectations on datasets.

When events are received that don't match these expectations, Observability surfaces alerts to give insight into the efficiencies—or areas for improvement—across your data operations.

Instance conditions

An instance is the runtime execution of a journey, that is, a snapshot of events that occur in the components of a journey. To represent when work is expected to happen, Observability will start or end instances based on conditions you set.

Rules

When you've finished building a journey and defining its conditions, you can create rules for different events and triggers.

Observability can send an email or trigger a web request, so you can stay up-to-date with situations that matter to you, and only when it's relevant.