Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Last updated on

Get started with Genie ZeroOps

Preview

This feature is in Private Preview. To try it, reach out to your Databricks contact.

This page explains how to set up Genie ZeroOps and review, interact with, and resolve the insights it generates. For an overview, see Genie ZeroOps.

Requirements​

  • A Databricks workspace that is enrolled in the Genie ZeroOps Private Preview.
  • OWNER, CAN MANAGE, or CAN VIEW permission on the jobs, pipelines, or tables that you want to monitor.
  • To detect data quality issues, Genie ZeroOps enables data quality monitoring on the schemas and tables you choose to monitor. Monitoring jobs does not enable it. While the Genie ZeroOps Private Preview is free, data quality monitoring is billed separately at standard pricing.

Set up Genie ZeroOps​

The initial ZeroOps inbox, prompting you to configure the assets to monitor.

  1. In the sidebar, click Workflows icon. Jobs & Pipelines to open the Jobs & Pipelines page.

  2. Click the Open ZeroOps button.

  3. If you have not configured Genie ZeroOps yet, you are prompted to do so. Click the Sparkle genie code icon. Configure button to open the Genie Code chat.

  4. When Genie Code prompts you for which resources to monitor, select a suggested scope, or describe your own in natural language:

    prompt

    Tell Genie Code what to monitor, for example:

    all owned jobs

After you set the scope, Genie ZeroOps analyzes your selected assets, backfilling insights from the previous 24 hours for jobs that have already failed and for tables that are stale or incomplete. It then displays any insights it finds for issues within that scope.

You can select the Sparkle genie code icon. Configure button at any time to adjust what Genie ZeroOps monitors. See Update Genie ZeroOps configuration.

Review an insight and its root cause​

Besides opening the Genie ZeroOps inbox from the Jobs & Pipelines page, you can also access it from full page Genie Code, where it appears in the thread list as ZeroOps Inbox.

  1. In the inbox, click an open insight to open its thread.
  2. Review the root cause analysis, the impacted assets, and the proposed fix.
  3. Follow the link to the source, such as the notebook, where you make the change.

If you do not have CAN VIEW permission on the asset that Genie ZeroOps identifies as the root cause, the insight masks the information you do not have access to.

An open ZeroOps insight thread, showing what failed, the root cause analysis, and the supporting evidence.

Manage insights​

From an open insight, you can take the following actions:

  • Resolve: Marks the issue as fixed and removes the insight from the inbox. Genie ZeroOps also resolves an insight for you automatically when a failing job succeeds on a later run.
  • Not an issue: Marks a detected issue that does not need a fix and removes the insight from the inbox. If Genie ZeroOps detects the same issue again after seven days, the insight reappears.
  • Retry: Starts a new job run. Genie ZeroOps proposes this action when a job failure is transient and the operation is idempotent, meaning it can be safely re-run.

Update Genie ZeroOps configuration​

To change what Genie ZeroOps monitors after setup, click Sparkle genie code icon. Configure in the top-right corner of the inbox. A Genie Code chat opens where you describe the jobs, pipelines, and tables you want to include or exclude.

The ZeroOps inbox after configuration, with an open insight and the Configure button in the top-right corner.

Filter insights​

  1. Click Filter.
  2. Select a status, such as Resolved.
  3. Apply the filter to update the inbox.

Troubleshooting​

  • No insights appear after you set up Genie ZeroOps: Confirm that you have OWNER, CAN MANAGE, or CAN VIEW permission on the jobs, pipelines, or tables you expect to see. Genie ZeroOps monitors only the assets you have permission on.
  • An insight masks the root cause: You do not have CAN VIEW permission on the root-cause asset. To see the full details, request CAN VIEW permission on that asset.
On this page