"How Can I Resolve an Issue with PagerDuty + Discord Integration in Pipedream?"

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi, I stared using pipedream and created the first integration with PagerDuty + Discord.
But I faced with the problem.
PagerDuty app see title and description in the same, and description field didn’t send to trigger at all.
the screenshot was attached with json.
Could you help with it ?

2

Hello , I see on Pipedream source code that it emits the data as is without changing anything. So I suspect that this is because the incident data on PagerDuty has the same title and description. Would you mind checking on PagerDuty side?

3

sure, I created incident with other fileds

4

but was send to discord message is
Incident: [#2155] PipeDream Description: PipeDream Created_at: 2023-02-01T10:15:37Z Incident_url: https://faraway.pagerduty.com/incidents/Q1A3Z4OHSNH80X Status: triggered Sent via [pipedream.com/@/p_aNCpqgv?o=a&a=discord_webhook](http://pipedream.com/@/p_aNCpqgv?o=a&a=discord_webhook)

5

hm….I found needed filed in the details of

6

but couldn’t find it into edit mode for workflow.

7

Could you tap into the more button to see all data?

8

I couldn’t create a PagerDuty on my side so I couldn’t reproduce it

9

there are everything that available.

steps.trigger
{2}
context
{15}
id:
2L8JBb49ovS8D1BKb5zNjVl2l2A
ts:
2023-02-01T10:17:21.607Z
Copy Path
•
Copy Value
pipeline_id:
null
workflow_id:
p_aNCpqgv
deployment_id:
d_5Zs2ZjbP
source_type:
TRACE
verified:
false
hops:
null
test:
true
replay:
false
owner_id:
u_BAhrryr
platform_version:
3.36.1
workflow_name:
PagerDuty+Discord
resume:
null
trace_id:
2L8JBb49ovS8D1BKb5zNjVl2l2A
event
{3}
id:
5f7c0ba0-a219-11ed-9970-ba25fe468f29
event:
incident.trigger
incident
{30}
incident_number:
2155
title:
PipeDream
description:
PipeDream
created_at:
2023-02-01T10:15:37Z
status:
triggered
incident_key:
86be6d1fcb9e4979a9d91bc6e24cf621
service
{22}
id:
PKKTXGR
name:
Miniroyale-Prod
description:
Managed by Terraform
created_at:
2021-11-02T09:50:07Z
updated_at:
2022-09-13T14:32:36Z
status:
critical
teams
[0]
alert_creation:
create_alerts_and_incidents
addons
[0]
scheduled_actions
[0]
support_hours:
null
last_incident_timestamp:
2023-02-01T10:15:37Z
escalation_policy
{5}
id:
PH0JNTC
type:
escalation_policy_reference
summary:
Emergency
self:
https://api.pagerduty.com/escalation_policies/PH0JNTC
html_url:
https://faraway.pagerduty.com/escalation_policies/PH0JNTC
incident_urgency_rule
{2}
type:
constant
urgency:
high
acknowledgement_timeout:
600
auto_resolve_timeout:
null
integrations
[1]
metadata
{0}
type:
service
summary:
Miniroyale-Prod
self:
https://api.pagerduty.com/services/PKKTXGR
html_url:
https://faraway.pagerduty.com/service-directory/PKKTXGR
assignments
[1]
0
{2}
assigned_via:
escalation_policy
last_status_change_at:
2023-02-01T10:15:37Z
first_trigger_log_entry
{5}
id:
RQ0O4CLZIIVU7XW433MXRNYBL9
type:
trigger_log_entry_reference
summary:
Triggered through the website.
self:
https://api.pagerduty.com/log_entries/RQ0O4CLZIIVU7XW433MXRNYBL9
html_url
https://faraway.pagerduty.com/incidents/Q1A3Z4OHSNH80X/log_entries/RQ0O4CLZIIVU7XW433MXRNYBL9
alert_counts
{3}
all:
0
triggered:
0
resolved:
0
is_mergeable:
true
escalation_policy
{5}
id:
PH0JNTC
type:
escalation_policy_reference
summary:
Emergency
self:
https://api.pagerduty.com/escalation_policies/PH0JNTC
html_url:
https://faraway.pagerduty.com/escalation_policies/PH0JNTC
teams
[0]
impacted_services
[1]
0
{5}
pending_actions
[0]
acknowledgements
[0]
basic_alert_grouping:
null
alert_grouping:
null
last_status_change_by
{5}
id:
PKKTXGR
type:
service_reference
summary:
Miniroyale-Prod
self:
https://api.pagerduty.com/services/PKKTXGR
html_url:
https://faraway.pagerduty.com/service-directory/PKKTXGR
metadata
{0}
external_references
[0]
urgency:
low
id:
Q1A3Z4OHSNH80X
type:
incident
summary:
[#2155] PipeDream
self:
https://api.pagerduty.com/incidents/Q1A3Z4OHSNH80X
html_url:
https://faraway.pagerduty.com/incidents/Q1A3Z4OHSNH80X
alerts
[0]
10

hm…can’t send more useful view….sorry

11

Hello , I think I understand the issue. Pipedream PagerDuty source just include some fields when it received an event from PagerDuty. Unfortunately, the field you needed (channel.details ) is not included

I’ve created a ticket to add this field and added it to Pipedream prioritized backlog: [ENHANCMENT] PagerDuty: New or Updated incident - add more data in event body · Issue #5377 · PipedreamHQ/pipedream · GitHub. Please subscribe to the ticket to see when it is done!

12

thanks for your support.