<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Pagerduty on Daniel Schaaff</title>
    <link>https://danielschaaff.com/tags/pagerduty/</link>
    <description>Recent content in Pagerduty on Daniel Schaaff</description>
    <generator>Hugo -- 0.147.4</generator>
    <language>en</language>
    <lastBuildDate>Tue, 21 Nov 2017 16:37:54 +0000</lastBuildDate>
    <atom:link href="https://danielschaaff.com/tags/pagerduty/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Exporting Pagerduty Incident Data</title>
      <link>https://danielschaaff.com/posts/2017/exporting-pagerduty-incident-data/</link>
      <pubDate>Tue, 21 Nov 2017 16:37:54 +0000</pubDate>
      <guid>https://danielschaaff.com/posts/2017/exporting-pagerduty-incident-data/</guid>
      <description>&lt;p&gt;Pagerduty provides a built-in way to export your incident data but only a limited number of data fields are available on the basic plan. Rather than upgrade you can use the API to export the data to a CSV. I found this &lt;a href=&#34;https://gist.github.com/ryanhoskin/b9c305274627c783f0d7&#34;&gt;gist&lt;/a&gt; listed &lt;a href=&#34;https://community.pagerduty.com/t/reporting-using-our-api-to-create-custom-reports/464&#34;&gt;here&lt;/a&gt;. The python script works great but some of my incident messages contained JSON data that threw off Excel when opening the CSV. I slightly modified the script with character escaping to work around this (lines 98- 107).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
