Skip to main content
Last updated on

Tines

Preview

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

Export Lakewatch alerts to a Tines story. When an alert is created, Lakewatch posts a JSON event to a Tines webhook, and your Tines story decides what happens with it. For how export behaves across destinations, see Alert destinations.

Export to Tines is one-way, from Lakewatch to Tines. Lakewatch sends the event through a Tines webhook action, authenticating with a webhook secret that you store as a Unity Catalog secret.

How the event is delivered​

  • On alert creation: Lakewatch posts a JSON event with the event_type lakewatch.alert.created. The payload uses the same schema and field names as the generic webhook destination, so a Tines story can read the same fields.
  • On alert updates: when update delivery is enabled for the destination, Lakewatch also posts a lakewatch.alert.updated event when the state, title, severity, description, classification, or assignee of an already-exported alert changes. When an alert closes, you receive an updated event with alert_state set to RESOLVED or DUPLICATE. There's no separate close event. To enable update delivery, select Also send alert updates in the settings. See Configure settings.
  • Your story decides the outcome: a successful export means Tines received the event, not that your story acted on it.
warning

Lakewatch sends each event one time. If delivery to Tines fails, Lakewatch records the failure and doesn't resend the event. The alert still appears in Lakewatch.

Use data.alert_id to match events to the same alert. With update delivery enabled, one alert produces a created event and later updated events, so check event_type to tell them apart. delivery_attempt_id changes on every delivery, so it can't tell you whether two events are about the same alert.

Prerequisites​

Set up the Tines webhook​

In your Tines story, add an inbound webhook action and configure it to authenticate with a secret:

  1. Add a Webhook action to your story.
  2. Set the action to require a secret, sent as a header (Secret access mode). Note the webhook URL and the secret.

For details, see the Tines webhook action documentation.

The webhook URL must be a webhook action URL, in the form https://<tenant>.tines.com/webhook/<path>, and reachable from the public internet. Lakewatch can't deliver to private networks, such as endpoints behind Private Link.

Store the webhook secret as a Unity Catalog secret​

Store the Tines webhook secret in a Unity Catalog secret in the __lakewatch schema of your Lakewatch environment's catalog. Select secret lists secrets from that schema, and Create secret creates one there. Lakewatch stores only the secret name, not the secret value.

You can create this secret ahead of time in <catalog>.__lakewatch, or create it while configuring Tines export with the Create secret button. Either way, creating a secret requires USE CATALOG on the catalog and either ownership of the __lakewatch schema or both CREATE SECRET and USE SCHEMA on it. For the steps, see Create a secret.

Required permissions​

To configure Tines export, you need the following:

  • READ SECRET on the Unity Catalog secret that holds the webhook secret, or on its parent schema or catalog. Lakewatch checks that you can read the secret when you save the configuration. To grant it, see Manage permissions on secrets.
  • The MANAGE privilege on your Lakewatch environment's catalog. See Configure settings.

To change the webhook secret, update the value of the same Unity Catalog secret. 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.

Set up Tines as an alert destination​

Configure a Tines destination for alerts in the Alerts settings section.

  1. In the Lakewatch sidebar, go to Settings, then open Alerts.
  2. Under Delivery, set Alert destination to Tines.
  3. In Webhook URL, enter the Tines webhook action URL (https://<tenant>.tines.com/webhook/<path>).
  4. For Webhook secret, click Select secret to choose the secret that holds the webhook secret, or click Create secret to create one from the webhook secret without leaving the page. The field shows the secret's name, not its value.
  5. (Optional) To also receive lakewatch.alert.updated events, select Also send alert updates.
  6. Save your changes.

For the full alert settings reference, see Configure settings.

Troubleshooting​

  • Events don't reach your story: the webhook URL isn't a Tines webhook action URL, or the story is disabled. Confirm the URL is in the https://<tenant>.tines.com/webhook/<path> form and the story is live.
  • The configuration doesn't save: you don't have permission to read the Unity Catalog secret, the secret is in a different catalog than your Lakewatch environment, or the webhook URL doesn't use HTTPS or points to a private network. Confirm your access to the secret, its catalog, and the webhook URL.
  • Your secret isn't listed in Select secret: Select secret lists only the secrets you can access in the __lakewatch schema of your environment's catalog. Store the secret there, or ask for READ SECRET on it.
  • Lakewatch reports a successful export but nothing happens in Tines: a 2xx response means Tines accepted the event, not that your story acted on it. Check your Tines story logic.
  • You rotated the webhook secret: update the Unity Catalog secret with the new value. No change to the export configuration is needed.
On this page