Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Add incident notes to the pagerduty integration

Answered
Sallie Walecka User

Connector name: Pagerduty 

Table name: log_entries

Column to add: incident_notes 

API documentation link:

https://developer.pagerduty.com/api-reference/a1ac30885eb7a-list-notes-for-an-incident

https://fivetran.com/docs/connectors/applications/pagerduty#schemainformation

 

Additional details: I would like to be able to grab the notes from an incident in pagerduty and see them in my snowflake table. I think it most naturally fits into log_entries but I'm not overly concerned on what field it ends up in as long as it can get joined with the incident_id 

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Syead Mujtaba Imam Rizwi Fivetranner

    Hi Sallie,

    Thank you for the request. We have added this to our active backlog and have confirmed that the PagerDuty API has a dedicated endpoint for listing notes per incident. I would love to understand your use case a bit better — are you looking to surface these notes in a separate table joinable to log_entries, or would a notes column on the existing table work? Any context about your reporting setup would help us scope this correctly. We will keep you updated on this thread as we make progress.

  • Sallie Walecka User

    I am hoping to use the notes to add free-form tagging so I can report on the # of alerts with notes that match certain substring. This will help us categorize alerts to understand how our system is going wrong and what sort of resolutions we are driving. A notes column on the existing table could work. All we really need is to join incident -> notes so a separate table would work fine as well as the notes column could be of a large size.