Skip to content

Commit 14fbae8

Browse files
committed
Merge remote-tracking branch 'origin/main' into prod_guidance
2 parents 4629acb + 13c146b commit 14fbae8

File tree

7 files changed

+16
-16
lines changed

7 files changed

+16
-16
lines changed

deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ The PagerDuty integration consists of the following parts:
8282

8383
**AutoOps configuration**
8484

85-
1. Add a new PagerDuty endpoint using the PagerDuty configuration application key.
85+
1. Add a new PagerDuty connector using the PagerDuty configuration application key.
8686
2. To receive Slack notifications, add a notification filter. Scroll down the Notification page and click **Add**.
8787
3. Fill in the filter details.
8888
4. Select the events that should be sent to this output.
@@ -100,8 +100,8 @@ To set up a webhook to send AutoOps notifications to a Slack channel, go through
100100
6. Toggle the **Activate Incoming Webhooks** to On.
101101
7. Click **Request to Add New Webhook**.
102102
8. Select a Slack channel from the list to receive the notifications and click **Allow**.
103-
9. Copy the webhook URL to set up the webhook notification endpoint in AutoOps.
104-
10. Add the webhook URL when creating the endpoint.
103+
9. Copy the webhook URL to set up the webhook notification connector in AutoOps.
104+
10. Add the webhook URL when creating the connector.
105105

106106

107107
### VictorOps [ec-autoops-victorops]
@@ -115,7 +115,7 @@ The VictorOps integration consists of the following parts:
115115

116116
**AutoOps configuration**
117117

118-
1. Add a new PagerDuty endpoint using the PagerDuty configuration application key.
118+
1. Add a new PagerDuty connector using the PagerDuty configuration application key.
119119
2. To receive Slack notifications, add a notification filter. Scroll down the Notification page and click Add.
120120
3. Fill in the filter details.
121121
4. Select the events that should be sent to this output.
@@ -137,7 +137,7 @@ The Opsgenie integration consists of the following parts:
137137

138138
1. Open AutoOps and go to **User Profile**. Then, select **Notifications**.
139139
2. Click **Add** and select **Opsgenie** from the dropdown list.
140-
3. Name your endpoint and add Api Key from opsgenie API configuration. Click the validate button to make sure that your notification setting is working. Don’t forget to save your notification endpoint!
140+
3. Name your connector and add Api Key from opsgenie API configuration. Click the validate button to make sure that your notification setting is working. Don’t forget to save your notification connector!
141141
4. To receive notifications on Opsgenie, you need to add a notification filter. Scroll down the **Notification** page and click **Add**.
142142
5. Fill in the filter details.
143143
6. Select events that should be sent to this output.
@@ -151,7 +151,7 @@ Save the URL displayed during the creation of the incoming webhook, as you will
151151

152152
**AutoOps configuration**
153153

154-
1. Add a new MS team endpoint using the URL from Microsoft Teams.
154+
1. Add a new MS team connector using the URL from Microsoft Teams.
155155
2. To receive notifications into Microsoft Teams, you need to add a notification filter. Scroll down the Notification page and click Add.
156156
3. Fill in the filter details.
157157
4. Select events that should be sent to this output.
@@ -163,7 +163,7 @@ A webhook enables an application to provide other applications with real-time in
163163

164164
**How to add a webhook notification**
165165

166-
1. Go to **Settings****Notifications******Endpoint settings** and click **Add**.
166+
1. Go to **Settings****Notifications******Connector settings** and click **Add**.
167167
2. Select Webhook from the drop-dowon list and enter the following details:
168168

169169
* Name: It must be a unique name for this webhook.
@@ -191,7 +191,7 @@ A webhook enables an application to provide other applications with real-time in
191191
5. Optionally, you can test the webhook integration by using the [webhook.site](https://webhook.site/#!/view/fe9d630e-2f01-44b7-9e41-ef9520fbe9a7).
192192

193193
::::{note}
194-
When the Endpoint settings have been completed, continue to set up the notification filter to define which events you’d like to be notified about.
194+
When the connector settings have been completed, continue to set up the notification filter to define which events you’d like to be notified about.
195195
::::
196196

197197
## Notifications report [ec-notification-report]

reference/data-analysis/observability/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,10 @@ mapped_pages:
88

99
Learn about the key metrics displayed in the Infrastructure app and how they are calculated.
1010

11-
* [Host metrics](/reference/data-analysis/observability/observability-host-metrics-serverless.md)
12-
* [Container metrics](/reference/data-analysis/observability/observability-container-metrics-serverless.md)
13-
* [Kubernetes pod metrics](/reference/data-analysis/observability/observability-kubernetes-pod-metrics-serverless.md)
14-
* [AWS metrics](/reference/data-analysis/observability/observability-aws-metrics-serverless.md)
11+
* [Host metrics](/reference/data-analysis/observability/observability-host-metrics.md)
12+
* [Container metrics](/reference/data-analysis/observability/observability-container-metrics.md)
13+
* [Kubernetes pod metrics](/reference/data-analysis/observability/observability-kubernetes-pod-metrics.md)
14+
* [AWS metrics](/reference/data-analysis/observability/observability-aws-metrics.md)
1515

1616

1717

reference/data-analysis/observability/observability-aws-metrics-serverless.md renamed to reference/data-analysis/observability/observability-aws-metrics.md

File renamed without changes.

reference/data-analysis/observability/observability-container-metrics-serverless.md renamed to reference/data-analysis/observability/observability-container-metrics.md

File renamed without changes.

reference/data-analysis/observability/observability-host-metrics-serverless.md renamed to reference/data-analysis/observability/observability-host-metrics.md

File renamed without changes.

reference/data-analysis/observability/observability-kubernetes-pod-metrics-serverless.md renamed to reference/data-analysis/observability/observability-kubernetes-pod-metrics.md

File renamed without changes.

reference/toc.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -257,10 +257,10 @@ toc:
257257
- file: data-analysis/machine-learning/ml-time-functions.md
258258
- file: data-analysis/observability/index.md
259259
children:
260-
- file: data-analysis/observability/observability-host-metrics-serverless.md
261-
- file: data-analysis/observability/observability-container-metrics-serverless.md
262-
- file: data-analysis/observability/observability-kubernetes-pod-metrics-serverless.md
263-
- file: data-analysis/observability/observability-aws-metrics-serverless.md
260+
- file: data-analysis/observability/observability-host-metrics.md
261+
- file: data-analysis/observability/observability-container-metrics.md
262+
- file: data-analysis/observability/observability-kubernetes-pod-metrics.md
263+
- file: data-analysis/observability/observability-aws-metrics.md
264264
- file: data-analysis/kibana/canvas-functions.md
265265
children:
266266
- file: data-analysis/kibana/tinymath-functions.md

0 commit comments

Comments
 (0)