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
text: "## PagerDuty incident trigger\n\nThis node listens for new incidents created in PagerDuty.\n\nWhen an incident is triggered, the event data flows downstream for processing.\n\n\n### To set up\n1. Click the node to open the sidebar configuration.\n2. Follow the instructions to connect your PagerDuty account.\n3. Select the service(s) and urgency levels to monitor."
166
-
width: 380
164
+
height: 282
165
+
text: "### 1. Listen to external resources\n\nTrigger components listen for events from external systems, in this case, we are listening to new triggered incidents on PagerDuty\n___\nTo use this example, connect your Pager Duty accounts:\n\n- Click each node\n- Follow the connection instructions for connecting PagerDuty\n- Go back to the node settings to configure Services you want to listen to, and set up other filters\n"
166
+
width: 460
167
167
metadata: null
168
168
position:
169
-
x: 415
170
-
"y": 16
169
+
x: 353
170
+
"y": 78
171
171
component: null
172
172
blueprint: null
173
173
trigger: null
174
174
widget:
175
175
name: "annotation"
176
176
isCollapsed: false
177
-
appInstallation: null
177
+
integration: null
178
+
errorMessage: ""
179
+
warningMessage: ""
180
+
- id: "merge-merge-1fzi6q"
181
+
name: "merge"
182
+
type: "TYPE_COMPONENT"
183
+
configuration:
184
+
enableStopIf: false
185
+
enableTimeout: true
186
+
executionTimeout:
187
+
unit: "minutes"
188
+
value: 2
189
+
metadata: null
190
+
position:
191
+
x: 2079
192
+
"y": 430
193
+
component:
194
+
name: "merge"
195
+
blueprint: null
196
+
trigger: null
197
+
widget: null
198
+
isCollapsed: false
199
+
integration: null
178
200
errorMessage: ""
179
201
warningMessage: ""
180
-
- id: "annotation-annotation2-mq2ini"
202
+
- id: "annotation-annotation2-hrxq4u"
181
203
name: "annotation2"
182
204
type: "TYPE_WIDGET"
183
205
configuration:
184
206
color: "yellow"
185
-
height: 253
186
-
text: "### Priority filter\n\nThis component filters incoming incidents to continue only if they are flagged as **P1** or **P2** priority.\n\nThe filter uses an **expression** that evaluates data from the event payload. \nPayloads contain all the information emitted by upstream components.\n\nOpen the node sidebar to see the filter expression and learn how to reference payload fields."
187
-
width: 392
207
+
height: 279
208
+
text: "### 2. Filter out incidents based on priority\n\nThe Filter component subscribes to events from external resources and forwards only those that contain \"P1\" or \"P2\" as the priority.\n\n___\nSuperPlane is an event-driven workflow engine that supports expressive, flexible conditions.\n\n- Click the Filter node to see how expressions are defined\n- Explore the [Data Flow](https://docs.superplane.com/concepts/data-flow/) documentation for more details\n"
209
+
width: 429
188
210
metadata: null
189
211
position:
190
-
x: 924
191
-
"y": 73
212
+
x: 894
213
+
"y": 79
192
214
component: null
193
215
blueprint: null
194
216
trigger: null
195
217
widget:
196
218
name: "annotation"
197
219
isCollapsed: false
198
-
appInstallation: null
220
+
integration: null
199
221
errorMessage: ""
200
222
warningMessage: ""
201
-
- id: "annotation-annotation3-8mge7o"
223
+
- id: "annotation-annotation3-7m2g95"
202
224
name: "annotation3"
203
225
type: "TYPE_WIDGET"
204
226
configuration:
205
227
color: "yellow"
206
-
height: 176
207
-
text: "### Data collection from Dash0\n\nThese components query Dash0 for multiple data points:\n\n**List Issues**: Retrieves all currently failing check rules from your Dash0 instance.\n\n**PromQL Queries**: Runs custom queries to fetch database memory and CPU usage metrics over the last 60 minutes.\n\nAll collected data is emitted downstream and becomes available for the AI summary and GitHub issue creation."
208
-
width: 1398
228
+
height: 265
229
+
text: "### 3. Collect metrics and health data\n\nThis step uses Dash0 to collect health signals from multiple sources and prepare data for a summary. The Dash0 List Issues component retrieves all failing checks, while Prometheus Query components fetch database memory and CPU usage metrics.\n\nA Merge component waits for all three data collection nodes to complete before the workflow continues.\n\n___\n\n**To use this with your dash0 instance:** \n- Ensure check rules are configured in Dash0\n- Review the queries used for database memory and CPU usage\n- Update the queries to match your environment\n"
230
+
width: 977
209
231
metadata: null
210
232
position:
211
-
x: 1470
212
-
"y": 161
233
+
x: 1459
234
+
"y": 80
213
235
component: null
214
236
blueprint: null
215
237
trigger: null
216
238
widget:
217
239
name: "annotation"
218
240
isCollapsed: false
219
-
appInstallation: null
241
+
integration: null
220
242
errorMessage: ""
221
243
warningMessage: ""
222
-
- id: "annotation-annotation4-fc9g80"
244
+
- id: "annotation-annotation4-31cjr5"
223
245
name: "annotation4"
224
246
type: "TYPE_WIDGET"
225
247
configuration:
226
248
color: "yellow"
227
-
height: 166
228
-
text: "### AI summary and GitHub issue\n\nWith access to all collected data, the **OpenAI** component generates a structured summary of the incident, including failing checks and database metrics.\n\nThe summary is then used to automatically create a **GitHub issue** for tracking and collaboration.\n\nTo use the OpenAI component, you need to connect your OpenAI account using an API key."
229
-
width: 878
249
+
height: 256
250
+
text: "### 4. Use AI to summarize data and create a GitHub issue\n\nRaw data emitted by upstream nodes is passed to the OpenAI component. The agent reviews this data and generates a summary in `markdown`, which is then used to create a GitHub issue with all relevant details.\n\n___\n- Connect your OpenAI account\n- Review how the prompt is configured and how upstream data is shared with the agent\n- After the issue is created, explore the payloads to see how data flows through the workflow\n- Learn how to select and manipulate payload data in the [Expressions](https://docs.superplane.com/concepts/expressions/) documentation\n"
0 commit comments