Setting Up Notifications for Incidents in DataHub and Workarounds for Open-Source Version

ui
1

Original Slack Thread

<@U06TM7M40RK> When a user creates an incident for a dataset, is there anyway that the owner of the dataset can receive a notification about the raised incident?

2

Yes, when an incident is created for a dataset, the owner of the dataset can receive a notification about the raised incident. According to the <https://github.com/datahub-project/datahub/blob/master/docs/managed-datahub/subscription-and-notification.md|DataHub documentation>, DataHub’s Subscriptions and Notifications feature allows users to receive real-time change alerts on data assets, including incident status changes. This feature supports notifications via Slack and Email, and it is possible to configure these notifications to alert dataset owners when incidents are raised.

To set up notifications for incidents, you can follow these steps:

  1. Configure Slack for Notifications: Ensure that Slack is configured within your DataHub instance. You can find the setup guide https://github.com/datahub-project/datahub/blob/master/docs/managed-datahub/slack/saas-slack-setup.md|here.

  2. Subscribe to Incident Notifications: Owners can subscribe to receive notifications about incident status changes. This can be done by selecting the types of changes they want to be notified about, such as incident status changes, in the subscription settings.

  3. Manage Notifications: Owners can manage their notification settings to ensure they receive relevant updates. This includes enabling or disabling notifications and selecting specific types of changes to be notified about.

Would you like more detailed guidance on setting up these notifications?

Sources:

3

<@U06TM7M40RK> is this only available for Acryl Cloud and not DataHub Open Source version?

4

Yes, the Subscriptions and Notifications feature, including the ability to receive notifications about incidents, is primarily available in DataHub Cloud (managed by Acryl) and not in the open-source version of DataHub. According to the <https://github.com/datahub-project/datahub/blob/master/docs/managed-datahub/subscription-and-notification.md|DataHub documentation>, features like Slack and email notifications are part of the managed DataHub Cloud offering. The open-source version does not natively support these notification features.

If you are using the open-source version and need similar functionality, you might need to implement custom solutions or integrations to achieve similar notification capabilities.

Would you like more detailed information on potential workarounds or custom implementations for the open-source version?

Sources:

5

<@U06TM7M40RK> yes, what are potential workarounds for the opensource version? Find out in this slack space if any of the users have discussed about potential implementations or shared any ideas around implementing notifications for open source version of DataHub?

6

For the open-source version of DataHub, users have discussed potential workarounds and implementations for notifications. Here are some insights and ideas shared by users in the DataHub Slack space:

  1. DataHub Actions Framework: One common approach is to use the <https://datahubproject.io/docs/actions/actions/slack|DataHub Actions Framework> to create custom notifications. This framework allows you to define actions that can be triggered by specific events, such as changes to datasets or incidents. You can configure these actions to send notifications via Slack or other messaging platforms.

  2. Custom Slack Integration: Users have implemented custom Slack integrations by using the Slack API to send messages to specific channels or users. This involves setting up a Slack app, obtaining the necessary tokens, and using the Slack API to send notifications based on events in DataHub.

  3. Webhook Notifications: Another approach is to use webhooks to send notifications to external systems. You can configure DataHub to trigger webhooks on specific events, and then use those webhooks to send notifications to Slack, email, or other platforms.

  4. Monitoring and Alerting with External Tools: Some users have integrated external monitoring and alerting tools, such as Prometheus or Grafana, to track DataHub events and send alerts based on specific conditions.

  5. Community Contributions: Users have expressed interest in contributing to the open-source project to add more robust notification features. Engaging with the community and contributing to the project could help bring these features to the open-source version.

These discussions and ideas indicate that while the open-source version does not have built-in notification features, there are several ways to implement custom solutions using existing tools and frameworks.

Would you like more detailed guidance on any of these approaches?

Sources:

  • <Slack Discussion on Notifications> :+1: 0 button :-1: 0 button :light_bulb: Hint: Mention @runllm in the thread for followups.