Notifications Innovation Release

With Hybrid Manager (HM), you can customize the types of notifications you want to receive. The two types of notification channels are:

User notifications — You can receive notifications via email, HM inbox, or both. These notifications are for all users who have enabled them and if their role allows it.

System notifications — You can receive notifications via email (mail group), webhook, Pager Duty, or any combination. These notifications are triggered once per event. System notifications are driven by activity log events, including cluster lifecycle changes (create, update, delete), security and index recommendations, automation task activity, and other platform events.

The user's role in HM determines the extent of their access to notification preferences. The notifications are categorized into the following preference sections:

• Account — For user notification channels.
• Global — For user and system notification channels.
• Projects — For user and system notification channels.

The notifications under the Account preference section are:

• New project role assigned to you
• Project role unassigned from you
• The personal access key is about to expire

The notifications under the Global preference section are:

• New project created
• The machine access key is about to expire

The notifications under the Projects preference section are:

• Active cluster paused
• Paused cluster reactivated
• Failed cluster maintenance upgrade
• User invited to project
• Failed third-party monitoring integration

Configuring notifications

Project owners/editors and organization owners/admins can enable/disable notifications for the events visible to them. They can receive notifications in the HM inbox, by email, or both.

Notification settings made by a user apply only to that user. If an email notification is enabled, the email is sent to the email address associated with the user's login.

For org-level and project-level notifications, HM determines who receives each notification by cross-referencing the event's target audience with each user's role and their enabled notification preferences. Both conditions must be met: the user's role must qualify them to receive that notification type, and they must have it enabled in their preferences. Account-level notifications are always delivered only to the individual user they concern.

System notification channels can be configured at the global level by the organization owner or at the project level by the project owner. By default, each organization's project inherits the global-level system notifications channel. However, you can enable/disable or reconfigure the system notifications channel at the project level to override the default settings.

Notification settings follow a scope hierarchy: global settings apply across all projects, and project-level settings override them. Configure at the lowest scope that fits your needs — global for organization-wide defaults, project-level for project-specific routing.

Configure notifications at the global level

Only the organization owner can set the global-level notifications.

Webhook

1. In the HM console, from your profile menu, select Settings.

2. Select the Notifications tab.

3. Select the edit icon next to Webhook and provide the details:

   • Host — The endpoint URL of the webhook.
   • Method — HTTP method for the request: POST or PUT.
   • HTTP Headers (optional) — Custom HTTP headers to include in the request, as key-value pairs.
   • Authentication — Select an authentication type and provide credentials:
     • Basic Auth — Enter an optional username and password.
     • Bearer Token — Provide a bearer token.

4. Select Save.

Pager Duty

Before configuring the Pager Duty notification channel:

• You need access to a Pager Duty account with elevated privileges.
• A Pager Duty service must be created and configured with Events API v2 integration.
• In your Pager Duty account, navigate to the desired service and access its Integrations settings.
• Add an Events API v2 integration and configure it according to your requirements.
• Copy the integration key (routing key) provided by Pager Duty for the newly created integration.

Then you can configure the channel:

1. In the HM console, from your profile menu, select Settings.
2. Select the Notifications tab.
3. Select the edit icon next to Pager Duty and set the Routing Key.
4. Select Save.

Email

1. In the HM console, from your profile menu, select Settings.

2. Select the Notifications tab.

3. Select the edit icon next to Email and enter the details:

   • Email To — Optionally, a group email address for system notifications. HM sends every system notification for this scope to this address — not just events relevant to the person who configured the channel. Use a shared inbox or distribution list, not a personal email address.
   • Email From — The email address that sends the notification.
   • Host — URL of the email service.
   • Port — Port of the email service.
   • Username — Username of the email service.
   • Password — Password of the email service.

   Note

   If Email To is set, HM delivers notifications to that address in addition to any eligible individual users — not instead of them. If Email To is left blank, only eligible individual users receive email notifications at their HM account email address.

4. Select Save.

Configure notifications at project level

Project-level notification settings can override global settings. Each project can have a unique configuration.

1. In the HM console, select the Projects tab.
2. Select any project.
3. Go to the Project Overview page.
4. In the left navigation, select Settings.
5. Select Notifications.
6. Specify settings as described in Webhook, Pager Duty, or Email.

Viewing notifications in the HM console

Users in the following roles can view the notifications:

• Organization owners can view the global notifications.
• Project owners/editors can view the project notifications.
• All users can view their account notifications.

Each notification indicates the level and project the user belongs to with multiple roles assigned in HM.

Select the bell icon at the top of the HM console to view notifications. You can read a notification, mark it as unread, or archive it.

Some notifications — particularly task-related ones — include a direct link to the affected resource. Selecting the link takes you to the relevant page, provided you have the required access permissions.

When you have unread broadcast notifications — platform-wide announcements such as maintenance windows — a persistent banner appears at the top of the console. If there are multiple unread broadcasts, banners stack. Select Mark as read on a banner to dismiss it.

Managing notification preferences

1. In the HM console, from your profile menu, select My Account.
2. Select the Notifications tab. Notifications are grouped by account, organizations, and projects available to you.
3. Scroll to the Account, Global, or Project section to view the events you want to manage.
4. Select the right arrow next to the entity to expand the list of events.
5. For each notification, you can:
   • Use the toggle next to the event name to opt in or out of receiving notifications for that event.
   • When the event toggle is enabled, select the check box for each channel (email, in-app, webhook, Pager Duty) to control which channels deliver that notification.