Alert destinations

Preview

Lakewatch is in Private Preview. To request access, reach out to your Databricks account team.

Lakewatch can export alerts to external systems. Open and track a Jira issue or a ServiceNow record, or trigger a Tines story or a webhook.

How export works

When you configure an export destination, Lakewatch sends each alert to that destination as soon as it's created in Lakewatch. Export is one-way, from Lakewatch to the destination. A failed export affects only delivery to the external system; the alert is still created in Lakewatch.

What happens after creation depends on the destination:

• ServiceNow and Jira keep a record in sync with the alert: Lakewatch creates a record and updates it as the alert changes.
• Webhooks and Tines receive a single event when the alert is created. Delivery is at most once, with no retry if it fails and no updates afterward.

See each destination's page for its exact delivery behavior.

Where to configure export

Configure export destinations in Lakewatch Settings, under Alerts. For the settings reference, see Configure settings.

Credentials and secrets

Destinations that use external authentication (Jira, ServiceNow, Tines) require you to store credentials in a Unity Catalog secret. After you save the export configuration, the secret name is stored but the secret value itself is never displayed in the UI (read-only). To update a secret, rotate it in Unity Catalog; the export uses the new value on the next alert export.

Secret permissions

The Unity Catalog privilege you need depends on the operation.

Operation	Privilege
Create a secret, ahead of time or with the inline Create secret button	USE CATALOG on the catalog, and either ownership of the schema or both CREATE SECRET and USE SCHEMA on the schema
Update or rotate a secret's value	WRITE SECRET on the secret
Read the secret	READ SECRET on the secret, or on its parent schema or catalog. Lakewatch reads the secret when you save the export configuration and each time it exports an alert.

Operation	Privilege
Create a secret, ahead of time or with the inline Create secret button	USE CATALOG on the catalog, and either ownership of the schema or both CREATE SECRET and USE SCHEMA on the schema
Update or rotate a secret's value	WRITE SECRET on the secret
Read the secret	READ SECRET on the secret, or on its parent schema or catalog. Lakewatch reads the secret when you save the export configuration and each time it exports an alert.

To grant these privileges, see Manage permissions on secrets.

Destinations

• • Jira
  • Create and update a Jira issue for an alert
• • ServiceNow
  • Create and update a ServiceNow record for an alert
• • Tines
  • Post a JSON event to a Tines story webhook when an alert is created
• • Webhook
  • Post each alert as a JSON payload to an HTTPS endpoint