Skip to content
This repository was archived by the owner on Apr 14, 2023. It is now read-only.

Commit d3656db

Browse files
author
Stephen Barlow
committed
Update docs for creating notifications to match UI
1 parent e3b6f95 commit d3656db

File tree

5 files changed

+12
-11
lines changed

5 files changed

+12
-11
lines changed

studio-docs/shared/obtain-graph-api-key.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ import {
1414

1515
**Otherwise**, proceed to the next step.
1616

17-
3. Open your graph's Settings page and scroll down to the API Keys section. Click **Create New Key**. Give your key a name, such as `Production`. This helps you keep track of each API key's use.
17+
3. Open your graph's Settings page and select the API Keys tab. Click **Create New Key**. Give your key a name, such as `Production`. This helps you keep track of each API key's use.
1818

19-
> If you don't see the API Keys section, you don't have sufficient permissions for your graph. Only organization members with the `Org Admin` or `Graph Admin` role can manage graph API keys. [Learn more about member roles.](https://www.apollographql.com/docs/studio/org/members/)
19+
> If you don't see the API Keys tab, you don't have sufficient permissions for your graph. Only organization members with the `Org Admin` or `Graph Admin` role can manage graph API keys. [Learn more about member roles.](https://www.apollographql.com/docs/studio/org/members/)
2020
2121
4. Copy the key's value. **For security, you cannot view an API key's value in Studio after creating it.**
2222

121 KB
Loading
21.5 KB
Loading

studio-docs/source/notification-setup.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,10 @@ Currently, Studio can send each of these notification types to the channel(s) in
3030
> For performance alerts, see [Performance alerts setup](./performance-alerts/#setup).
3131
3232
1. Go to your graph's Settings page in [Apollo Studio](https://studio.apollographql.com/).
33-
2. Select the **Notifications** tab.
34-
3. Click **Add notification** in the upper right.
35-
4. Choose a notification type and click **Next**.
33+
2. Select the **Reporting** tab.
34+
3. Click **Add notification** in the upper right:
35+
<img src="./img/add-new-alert.jpg" class="screenshot" width="500" alt="Add new alert button" />
36+
5. Select a notification type and click **Next**:
3637
<img src="./img/add-notification.jpg" class="screenshot" width="500" alt="Notification creation modal" />
3738
5. In the dropdown, select which [variant](./org/graphs/#managing-variants) of your graph you want to receive notifications for.
3839
6. Select an existing configured channel to send notifications to, or select which type of new channel you want to configure:

studio-docs/source/performance-alerts.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -24,14 +24,14 @@ Each performance alert you define can apply to either **a specific operation** o
2424
## Setup
2525

2626
1. Go to your graph's Settings page in [Apollo Studio](https://studio.apollographql.com/).
27-
2. Select the **Notifications** tab and scroll to the bottom of the page:
27+
2. Select the **Reporting** tab.
28+
3. Find the Performance Alerts card and click **Add a new alert**.
2829

29-
<img src="./img/integrations/perf_alert_setup.png" class="screenshot" alt="Performance alert" />
30+
<img src="./img/add-new-alert.jpg" class="screenshot" width="500" alt="Add new alert button" />
3031

31-
2. Click **Add new alert**.
32-
3. Configure the alert's **Operation Name**, **Trigger**, and **Trigger Value** to suit your needs.
33-
4. Select a **Channel** to send alerts to. You can select **New Channel** from the dropdown if you haven't yet configured the Slack channel or Pagerduty instance you want to use.
34-
5. Click **Done**.
32+
4. Configure the alert's **Operation Name**, **Trigger**, and **Trigger Value** to suit your needs.
33+
5. Select a **Channel** to send alerts to. You can select **New Channel** from the dropdown if you haven't yet configured the Slack channel or Pagerduty instance you want to use.
34+
6. Click **Create**.
3535

3636
## Threshold window
3737

0 commit comments

Comments
 (0)