Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Lakewatch is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage workspace-level previews.
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. If an export fails, the alert still appears in Lakewatch.
What happens after creation depends on the destination:
- ServiceNow and Jira: Lakewatch creates a record and keeps it in sync with the alert, updating it as the alert changes.
- Webhooks and Tines: Lakewatch sends an event when the alert is created. To also send an event when the alert changes, select Also send alert updates in the settings. Updates cover changes to the alert's state, title, severity, description, classification, or assignee, including when it's closed. Lakewatch tries each delivery one time, with no retry if it fails.
See each destination's page for its exact delivery behavior.
Where to configure export
Configure export destinations in Lakewatch Settings > Alerts, under Delivery. To stop exporting alerts, set Alert destination to Off. To edit these settings, you need the MANAGE privilege on your Lakewatch environment's catalog. For the settings reference, see Configure settings.
You can also export system errors. Configure system error export under Settings > System errors > Delivery. It supports the same destination types as alerts, but you configure it separately, so system errors can go to a different destination. For webhooks and Tines, select Also send system error updates to also send an event when a system error changes.
Credentials and secrets
Jira, ServiceNow, and Tines need a credential, which you store in a Unity Catalog secret. Store the secret in the __lakewatch schema of your Lakewatch environment's catalog. In the settings, Select secret lists secrets from that schema, and Create secret creates one there. Lakewatch stores only the secret name, and the settings show the name, not the value.
- To change the credential, rotate the secret's value in Unity Catalog. Lakewatch uses the new value on the next export, with no change to the settings.
- To use a different secret, click Select secret or Create secret in the settings and save.
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 environment's catalog, and either ownership of the __lakewatch schema or both CREATE SECRET and USE SCHEMA on it |
| 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 checks this privilege when you save the export settings. |
To grant these privileges, see Manage permissions on secrets.
Destinations
| Destination | Description |
|---|---|
| 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 |