You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: advocacy_docs/edb-postgres-ai/console/using/notifications.mdx
+84-8Lines changed: 84 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,20 @@ navTitle: Notifications
4
4
description: "Use notifications to get an alert for the different types of events occurring in your EDB Postgres AI account, organizations, and projects."
5
5
redirects:
6
6
- /biganimal/latest/administering_cluster/notifications/ #generated for BigAnimal URL path removal branch
7
+
deepToC: true
8
+
indexdepth: 3
7
9
---
8
10
9
-
With EDB Postgres AI, you can opt to get specific types of notifications and receive both in-app and email notifications.
11
+
With EDB Postgres AI, you can customize the types of notifications you want to receive. There are two types of notifications channels:
10
12
11
-
Different types of events are sent as notifications. Users with different roles can configure the preferences to receive these notifications in the in-app inbox, by email, or both.
13
+
- User notifications channels - where you can receive notifications on email or in-app inbox or both. These notifications are for all users who have enabled them and are eligible to receive the notifications for that event.
14
+
- System notifications channels - where you can receive notifications on slack or webhook or pagerduty or all. These notifications are designed to trigger once per event, primarily for automating tasks within the user's organization.
15
+
16
+
Different types of events are sent as notifications. Users with different roles can configure the preferences to receive these notifications.
12
17
The notifications are categorized into the following preference sections:
13
-
- Account
14
-
- Organizations
15
-
- Projects
18
+
-**Account** - only for user notification channels
19
+
-**Organizations** - for user and system notification channels both
20
+
-**Projects** - for user and system notification channels both
16
21
17
22
The notifications under the **Account** preference section are:
18
23
@@ -44,12 +49,83 @@ The notifications under the **Projects** preference section are:
44
49
45
50
## Configuring notifications
46
51
47
-
The project owners/editors and organization owners/admins can configure the notifications for the events visible to them. They can choose if they want to receive notifications in the in-app inbox, by email, or both. They can also configure email notifications for their teams in their organization.
48
-
49
-
Project-level notifications are configured in the project.
52
+
The project owners/editors and organization owners/admins can enable/disable the notifications for the events visible to them. They can choose if they want to receive notifications in the in-app inbox, by email or both.
50
53
51
54
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.
52
55
56
+
System notification channels can be configured at Organization-level by organization owner or at Project-level by project owner. By default, the Organization-level system notifications channel are inherited by each project of that organization. However you can enable/disable or re-configure the system notifications channel at the Project-level to override the default settings.
57
+
58
+
This steps shows how to configure the system notification channels at Organization-level:
59
+
60
+
### Configure Slack notification channel
61
+
62
+
To configure Slack notification channel:
63
+
64
+
1. Log in to the EDB Postgres AI console.
65
+
1. From the menu under your name in the top-right panel, select **Settings**.
66
+
1. Select the **Notifications** tab. Options available are Webhook, Slack, and Pager Duty.
67
+
1. Select **Slack** and a window pops-up, provide the following details:
68
+
1. Access token - provide a slack bot access token.
69
+
1. Slack Channel on which notification are to be sent. For example: #general, #alerts, #notifications, etc.
70
+
1. Select **Save** button
71
+
72
+
!!!note
73
+
Before configuring slack notification channel, you need to create the slack app and grant the following permissions:
74
+
-`chat:write`
75
+
-`im:write`
76
+
-`users:read.email`
77
+
-`users:read`
78
+
79
+
Once the slack app is created and installed on the slack workspace, you can use the slack bot user OAuth token of the slack app to setup the slack channel.
80
+
81
+
Also make sure to add the created slack app to the slack channel of your choice.
82
+
!!!
83
+
84
+
85
+
### Configure Webhook notification channel
86
+
87
+
To configure Webhook notification channel:
88
+
89
+
1. Log in to the EDB Postgres AI console.
90
+
1. From the menu under your name in the top-right panel, select **Settings**.
91
+
1. Select the **Notifications** tab. Options available are Webhook, Slack, and Pager Duty.
92
+
1. Select **Webhook** and provide the details on the pop-up window:
93
+
1. Host URL of the Webhook
94
+
1. Method of the Webhook - POST or PUT
95
+
1. Optionally provide any of these authentication parameters
96
+
1. For Basic Auth:
97
+
1. Username
98
+
2. Password
99
+
2. For Bearer Token:
100
+
1. Bearer Token
101
+
2. Select **Save** button.
102
+
103
+
### Configure Pager Duty notification channel
104
+
105
+
To configure Pager Duty notification channel:
106
+
107
+
1. Log in to the EDB Postgres AI console.
108
+
1. From the menu under your name in the top-right panel, select **Settings**.
109
+
1. Select the **Notifications** tab. Options available are Webhook, Slack, and Pager Duty.
110
+
1. Select **Pager Duty** and provide the details on the pop-up window:
111
+
1. Set Routing Key(integration key).
112
+
2. Select **Save** button.
113
+
114
+
!!!note
115
+
Before configuring Pager Duty notification channel:
116
+
- You need to have access to a Pager Duty account with elevated privileges.
117
+
- Pager Duty Service created and configured with Events API v2 integration.
118
+
- In your PagerDuty account, navigate to the desired Service and access its "Integrations" settings.
119
+
- Add a new "Events API v2" integration and configure it according to your requirements.
120
+
- Copy the Integration Key(routing key) provided by PagerDuty for the newly created integration.
121
+
!!!
122
+
123
+
To configure the system notifications channel at Project-level:
124
+
- Go to **Project Overview** page
125
+
- Select **Settings** on the left-side menu
126
+
- Select **Notifications**
127
+
- Follow the steps as mentioned above for Organization-level for each of the system notification channel.
128
+
53
129
## Viewing notifications
54
130
55
131
Users in the following roles can view the notifications:
0 commit comments