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: docs/integration/external-integrations/pagerduty-integration.mdx
+74-66Lines changed: 74 additions & 66 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ This guide walks you through creating a PagerDuty Service, setting up the integr
14
14
15
15
## Alert Types
16
16
17
-
You can customize alerts sent from Device42 by choosing from wide range of violating conditions from a set of **Rule Types**, such as Discovery, Operating System, Part Model, Software, and more. Choose from a range of available triggers for each rule type that include, but are not limited to, the following:
17
+
You can customize alerts sent from Device42 by choosing from a wide range of violating conditions within a set of **Rule Types**, such as Discovery, Operating System, Part Model, Software, and more. Choose from various available triggers for each rule type. These triggers include, but are not limited to, the following:
18
18
19
19
Operating System
20
20
@@ -54,18 +54,18 @@ System
54
54
55
55
## How it Works
56
56
57
-
Device42 metrics that fall outside of a designated range or meet a given criteria will send an alert to a service in PagerDuty.
57
+
When a Device42 metric falls outside of a designated range or meets a given criterion, Device42 sends an alert to a service in PagerDuty.
58
58
59
59
## Requirements
60
60
61
-
- Device42 version 16.14.00 and later.
62
-
- Network access to one of the Device42 Cloud Connectors. For example,`connect.device42.net` (US) or `connect-eu.device42.net` (EU).
61
+
- Device42 version 16.14.00 and later
62
+
- Network access to one of the Device42 Cloud Connectors, such as`connect.device42.net` (US) or `connect-eu.device42.net` (EU)
63
63
64
64
## Support
65
65
66
66
If you need help with this integration, please contact **Device42 Support** using any of our listed contact methods.
67
67
68
-
-**Hours of Operation:** Monday-Friday, 9AM – 6PM EST
68
+
-**Hours of Operation:** Monday-Friday, 9 am–6 pm EST
@@ -79,19 +79,20 @@ The Device42 integration in PagerDuty will generate a key that you'll use in Dev
79
79
### Create a New Service with Integration
80
80
81
81
To create a new service, go to **Services > Service Directory** and click the **+ New Service** button.
82
-
The setup will guide you to selecting an integration in the final step.
83
82
84
-
- To create a new service, click the **+ New Service** button and enter a **Name** and optional **Description** for the new service. Continue with steps 2 and 3 of the guided setup until you get to the [fourth **Integration** step](#select-the-device42-integration).
83
+
Follow the guided setup until you reach the [fourth **Integration** step](#select-the-device42-integration).
85
84
86
85
:::tip
87
86
Please refer to PagerDuty's [Configuring Services and Integrations](https://support.pagerduty.com/docs/services-and-integrations#section-configuring-services-and-integrations) docs page for details on the service options.
88
87
:::
89
88
90
-

89
+

91
90
92
-
- To add the Device42 integration to an existing PagerDuty Service, click the name of the service, open the **Integrations** tab, then click the **+ Add New Integration** button.
91
+
### Add Integration to an Existing Service
93
92
94
-

93
+
To add the Device42 integration to an existing PagerDuty Service, click the name of the service, open the **Integrations** tab, then click the **+ Add New Integration** button.
94
+
95
+

95
96
96
97
### Select the Device42 Integration
97
98
@@ -101,7 +102,7 @@ When you get to the **Integration** step, search for and select **Device42**, th
101
102
102
103
### Copy the Integration Key
103
104
104
-
An **Integration Key** will be generated. Keep this key saved in a safe place, as it will be used when you configure the integration with Device42 in the next section. You won't need the **Integration URL** generated by PagerDuty.
105
+
An **Integration Key** will be generated. Keep this key saved in a safe place, as you'll use it to configure the integration with Device42 in the next section. You won't need the **Integration URL** generated by PagerDuty.
105
106
106
107

107
108
@@ -113,12 +114,15 @@ The Device42 setup includes configuring your [Cloud Services](/integration/exter
113
114
114
115
The [Cloud Connector](/integration/external-integrations/device42-cloud-connector-overview.mdx) provides a secure and reliable way to route external integration communication.
115
116
116
-
From the Device42 Dashboard, go to **Tools > Integrations > Cloud Services** and click **Edit** at the top-right of the page.
117
+
From the Device42 Dashboard, go to **Tools > Integrations > Cloud Services** and click **Edit** at the top right of the page.
118
+
119
+
Enter your Device42 instance URL in the **D42 URL for SaaS apps** field, for example, `https://192.168.92.130/`.
120
+
121
+
Fill in the **Company Name** and **Email** to be used as a contact for any integration-related incidents.
117
122
118
-
1. Fill your Device42 instance URL in **D42 URL for SaaS apps**, for example `https://192.168.92.130/`.
119
-
2. Fill in the **Company Name** and **Email** to be used as a contact for any integration-related incidents.
120
-
3. Select the **USA** option from the **Cloud Connector** drop down list if this is the region closest to you, otherwise select **Europe**. PagerDuty works best with a USA Cloud Connector.
121
-
4. Click **Save** and the page will reload, displaying your **Device42 GUID**.
123
+
Select the **USA** option from the **Cloud Connector** dropdown list if the USA is the region closest to you; otherwise, select **Europe**. PagerDuty works best with a USA Cloud Connector.
124
+
125
+
Click **Save** and the page will reload, displaying your **Device42 GUID**.
122
126
123
127
<ThemedImage
124
128
alt="Device42 Cloud Services"
@@ -132,14 +136,18 @@ From the Device42 Dashboard, go to **Tools > Integrations > Cloud Services** and
132
136
133
137
Navigate to **Tools > Integrations > External Integrations** and click **Create** on the top-right of the screen.
134
138
135
-
1. In the **URL** field, enter the domain of your PagerDuty account as it appears in the browser's address bar, for example, `https://device42demoacc.pagerduty.com`. Note this is not the **Integration URL** from the Device42 integration in PagerDuty.
136
-
2. Select **PagerDuty** from the **Type** drop down field.
137
-
3. In the **Token** field, input the **Integration Key** you got from the Device42 integration in PagerDuty:
138
-
- Click the **plus icon** to create a new Secret.
139
-
- In the pop-up window, click the **Create** button at the top right.
140
-
- Enter a **Username** that will act as an alias and be attached to the PagerDuty integration key for future reference.
141
-
- Paste the PagerDuty **Integration Key** in the **Password** field ensuring that there are no trailing white spaces or new line characters.
142
-
4.**Save** the External Integration.
139
+
In the **URL** field, enter the domain of your PagerDuty account as it appears in the browser's address bar, for example, `https://device42demoacc.pagerduty.com`. Note this is not the **Integration URL** from the Device42 integration in PagerDuty.
140
+
141
+
Select **PagerDuty** from the **Type** dropdown field.
142
+
143
+
In the **Token** field, input the **Integration Key** you got from the Device42 integration in PagerDuty:
144
+
145
+
- Click the **plus icon** to create a new Secret.
146
+
- In the pop-up window, click the **Create** button at the top right.
147
+
- Enter a **Username** that will act as an alias and be attached to the PagerDuty integration key for future reference.
148
+
- Paste the PagerDuty **Integration Key** in the **Password** field, ensuring that there are no trailing white spaces or new line characters.
149
+
150
+
**Save** the External Integration.
143
151
144
152
<ThemedImage
145
153
alt="Add external integration"
@@ -151,14 +159,14 @@ Navigate to **Tools > Integrations > External Integrations** and click **Create*
151
159
152
160
### Configure an Alert
153
161
154
-
You need to configure a Device42 alert to use the PagerDuty External Integration and route the alert message to PagerDuty. The following steps will configure a prohibited software alert, but any type of alert can be used and would have similar steps.
162
+
You need to configure a Device42 alert to use the PagerDuty External Integration and route the alert message to PagerDuty. The following steps configure a prohibited software alert, but any type of alert can be used and would have similar steps:
155
163
156
-
1. Go to **Analytics > Alerts > Setup Alerts** and click the **Create** button.
157
-
2. Under **Rule Type** select **Software**.
158
-
5. Under **Trigger** select **Prohibited Software Installed**.
159
-
6. For the **Alert Type** choose **Alert Integration**.
160
-
7. From the **Alert Integration** dropdown select your PagerDuty instance URL that should be populated.
161
-
8.**Save** the alert.
164
+
- Go to **Analytics > Alerts > Setup Alerts** and click the **Create** button.
165
+
- Under **Rule Type** select **Software**.
166
+
- Under **Trigger** select **Prohibited Software Installed**.
167
+
- For the **Alert Type** choose **Alert Integration**.
168
+
- From the **Alert Integration** dropdown, select your PagerDuty instance URL that should be populated.
169
+
-**Save** the alert.
162
170
163
171
<ThemedImage
164
172
alt="Configure alert settings"
@@ -170,12 +178,12 @@ You need to configure a Device42 alert to use the PagerDuty External Integration
170
178
171
179
## Test the Integration
172
180
173
-
To test that the condition triggers the alert as expected, designate a Software Component as **Prohibited** and add that software to a device.
181
+
To test that the condition triggers the alert as expected, designate a Software Component as **Prohibited** and add that software to a device:
174
182
175
-
1. Navigate to **Resources > Software Components > All Software Components**.
176
-
2. Click on the software component you want to set as prohibited and click the **Edit** button on the top-right.
177
-
4. Under **Software Type** select **Prohibited**.
178
-
5.**Save** the change.
183
+
- Navigate to **Resources > Software Components > All Software Components**.
184
+
- Click on the software component you want to set as prohibited and click the **Edit** button on the top-right.
185
+
- Under **Software Type** select **Prohibited**.
186
+
-**Save** the change.
179
187
180
188
<ThemedImage
181
189
alt="Software component settings"
@@ -185,12 +193,12 @@ To test that the condition triggers the alert as expected, designate a Software
185
193
}}
186
194
/>
187
195
188
-
Next, manually (without running a discovery job) associate the prohibited software with a device, which you can do in multiple ways like creating a new Software In Use record or new device with the prohibited software. In this example we'll edit an existing device to include the prohibited software.
196
+
Next, manually associate (without running a discovery job) the prohibited software with a device. You can do this in multiple ways, such as by creating a new Software In Use record or a new device with the prohibited software. In this example, we'll edit an existing device to include the prohibited software:
189
197
190
-
1. Go to **Resources > Compute > All Devices** and select a device.
191
-
2. Click **Edit** and scroll down to **Software In Use**.
192
-
3. Click **+ Add New** and choose from the **Software** dropdown, select the prohibited software (`libsqlite3-0` in the example).
193
-
4.**Save** the device to designate the software as prohibited and trigger the alert created in the steps above.
198
+
- Go to **Resources > Compute > All Devices** and select a device.
199
+
- Click **Edit** and scroll down to **Software In Use**.
200
+
- Click **+ Add New** and choose from the **Software** dropdown, select the prohibited software (`libsqlite3-0` in the example).
201
+
-**Save** the device to designate the software as prohibited and trigger the alert created in the steps above.
194
202
195
203
<ThemedImage
196
204
alt="Add prohibited software to device"
@@ -208,48 +216,48 @@ You can view incident details in PagerDuty.
Remember to undo the changes you made in Device42 when testing the instance – change the prohibited software type on the Software Component you used and remove the Software In Use entry from the device.
219
+
Remember to undo the changes you made in Device42 when testing the instance: Change the prohibited software type on the Software Component you used and remove the Software In Use entry from the device.
212
220
213
221
## How to Uninstall the Integration
214
222
215
-
To uninstall the integration, delete the Device42 integration in PagerDuty or disable its associated service, and in Device42 delete the External Integration.
223
+
To uninstall the integration, delete the Device42 integration in PagerDuty or disable its associated service. Then, in Device42, delete the External Integration.
216
224
217
225
### Delete the Integration in PagerDuty
218
226
219
227
In PagerDuty, navigate to **Services > Service Directory** and click on the service with the Device42 integration:
220
228
221
-
1. Go to the **Integrations** tab and click the black **gear icon**.
222
-
2. Select **Delete Integration**
223
-
3. Confirm the deletion when prompted.
229
+
- Go to the **Integrations** tab and click the black **gear icon**.
Alternatively, you can disable the service with the Device42 integration:
228
236
229
-
1. Go to **Services > Service Directory**.
230
-
2. On the right side of the service you want to disable, click the **More** dropdown menu.
231
-
3. Click **Disable Service** and click **Disable** on the confirmation dialog.
237
+
- Go to **Services > Service Directory**.
238
+
- On the right side of the service you want to disable, click the **More** dropdown menu.
239
+
- Click **Disable Service** and click **Disable** on the confirmation dialog.
232
240
233
241
### Delete the Integration in Device42
234
242
235
-
In Device42 navigate to **Tools > Integrations > External Integrations** and select the checkbox next to the PagerDuty integration you want to remove.
243
+
In Device42, navigate to **Tools > Integrations > External Integrations** and select the checkbox next to the PagerDuty integration you want to remove.
236
244
237
-
-From the **Actions** dropdown menu select **Delete with Detailed Confirmation**.
245
+
From the **Actions** dropdown menu, select **Delete with Detailed Confirmation**.
0 commit comments