Skip to main content
Sumo Logic

Collect Logs for PagerDuty

Steps to configure a Sumo Logic Collector and Source, and to create a PagerDuty Webhook.

Configure a Sumo Logic Collector and Source

In Sumo Logic, configure:

  1. A Hosted Collector.
  2. An HTTP Source. When you configure the HTTP Source, make sure to save the HTTP Source Address URL. You will need this to configure the PagerDuty Webhook.  

Create a PagerDuty Webhook

In PagerDuty, Webhooks allow you to receive HTTP callbacks when incident events happen in your PagerDuty account. Details about the event are sent via HTTP to a URL that you specify.

In PagerDuty, create a Webhook using the instructions here:

The Endpoint URL you are asked to supply in Step 6 is the HTTP Source Address URL from the HTTP Source you configured.  

Sample Log Message

               "pending_actions":[ ],
                  "name":"Data Collection",
                  "name":"Data Collection Policy",
                  "name":"Ben Newton",
                  "description":"long-rework-4/health/free_space__usr_sumo: Use too much 80.0 % of disk space (max: 80.0 %)"
                        "name":"Ben Newton",

Query Sample

Number of Incidents Assigned to Users

_sourceCategory=pagerduty assigned_to "incident.trigger"
| json "messages[0].type", "messages[0]", "messages[0].data.incident.created_on", "messages[0].data.incident.status", "messages[0].data.incident.urgency", "messages[0].data.incident.assigned_to[0]", "messages[0]", "messages[0]", "messages[0].data.incident.trigger_summary_data.description"  as type, incident_id, created_on, incident_status, incident_urgency, assigned_user, escalation_policy_name, service_name, incident_descrition
| where type = "incident.trigger" 
| count by assigned_user, incident_urgency
| transpose row  assigned_user column incident_urgency
| order by assigned_user asc