@marcus wrote:
Hey there,
I’m Marcus, a Site Reliability Engineer working at Xero out of our Auckland office.
We’re a fairly large customer with more than 100 on call users across a number of teams. I’m even personally on call as the secondary responder for our SRE team right now but thankfully it’s often quiet due to teams handling their own production issues
If you’re new to on call, it can seem daunting at first but it becomes second nature pretty quickly
Posts: 1
Participants: 1
@finningryan wrote:
Hey folks!
Just a quick intro - I’m Ryan from Vancouver, and I’m a recovering systems administrator
I’m currently working at Finning International, generally poking around in Azure DevOps Pipelines (think turbo-Jenkins!), Kubernetes, Terraform or Bash.
In a previous life I used PagerDuty to manage a web-scale operation and loved it - happy to be back to a familiar tool.
My on-call tip: always have a clear line to whatever incident report template you need by sticking a link to it in your alerts. Runbooks are pretty helpful in the same spot too. You never know when you just. can’t. find. the. link. at 3AM and just want to get back to sleep!
Posts: 1
Participants: 1
@adit wrote:
HI. I’m trying to integrate PagerDuty with my Jira Service Desk, but when I add a new service and in the integration type, I find the name “Jira”, it’s not showing anything.
Please guide how can I add Jira service to my PagerDuty, as it is very urgent.
Posts: 2
Participants: 1
@ChanderThakur wrote:
I have created the service(CloudWatch Integration) in PagerDuty using Terraform and now want to utilize service event rules to add actions on particular conditions.Could you please suggest me workaround for the same ? This would be great help for automation.
Posts: 2
Participants: 1
@cmoultrie wrote:
Hello. I’m an SRE at Pindrop in Atlanta, we’re heavy PagerDuty users and I have a few tools I’ve written around the API. Glad to be here.
Posts: 2
Participants: 2
@postiepoo wrote:
I’m a SDE from AWS that has some spare real estate on his laptop <3
Posts: 2
Participants: 2
@voidlily wrote:
I’m Lily and I’m an SRE at PagerDuty. I help manage AWS resources and tooling for other PagerDuty engineers to write the services that keep you notified on the things you care about.
Posts: 1
Participants: 1
@BrianK wrote:
Hi Community! Like many of you, I like stickers!
I also happen to be a PagerDuty user. I have been silently following the community for a few months, but coming out of the shadows now in hopes of increasing my sticker collection. If I learn some best practices along the way, sharing with other community members, all the better!
Brian
Posts: 2
Participants: 2
@gregu wrote:
I’m trying to configure Pager Duty as a sort of gate keeper to filter out low quality violations from New Relic ping tests. My goal is to trigger a Pager Duty alert through the escalation policy chain only if the server is down for more than 10 minutes. Right now we’re getting alerts in the middle of the night if the server is down for a few seconds.
I have my New Relic Alert Policy incident preferences set to open an incident every time a condition is violated and I’m running tests every 5 minutes. The Synthetic is set to search for an element that does not exist on the page to specifically trigger a violation for testing purposes only. I’ve configured an Event Rule so when the body contains “Ping” the following actions are performed:
* Route to [Backend Critical (New Relic)](https://24datainc.pagerduty.com/services/XXXX) * Suppressing until more than ` 2 alerts` received within `12 minutes` * Then stop processingI am artificially forcing 2 violations in a row New Relic with the hope that Pager Duty will filter out the first warning and trigger an incident to the escalation policy on the second but it seems like
a. New Relic is only sending Pager Duty one notification and
b. Pager Duty is receiving that first notification from NR and immediately sending it through the escalation policy.Any advice please?
Posts: 1
Participants: 1
@mbaxter wrote:
Hello! My name is Margo and I’m a Front-End Developer at PagerDuty. This is the biggest company I have worked at, and the most fun. Before coming here, I worked in startups for most of my career. I work remotely from Madison (my hometown) in the summer, and in Austin in the winter. When I’m not building front-end stuff, I’m probably out running trails or at the gym.
Posts: 1
Participants: 1
@jcalcada wrote:
In this age of extensive social networking, it is essential for organizations to monitor customer sentiment via solutions that monitor platforms such as twitter. This document provides guidance on how to create integration between a tweet analysis solution, and PagerDuty.
Use case:
Allow PagerDuty to create an incident whenever a tweet contains a predefined keyword and in the PagerDuty Infrastructure Health Console place a "T” marker on the graph.Prereqs:
These procedures assumes you have:
A PagerDuty account with admin authority
A twitter account with developer access (needed in order to get required API tokens)
A small server (virtual or otherwise) with python 2.7 or higher installed
strong textPART 1: PAGERDUTY SETUP:
Select Configuration/Services then create/modify a service you want to receive the tweet
notification on. Select the integration tab the click “new integration”Name your integration “Twitter Custom Event Transformer”, and select from the pulldown menu
“custom event transformer”, then choose an existing escalation policy. Since this service is
meant to be automatic you may wish to create a “no ops” escalation policy so no one gets
notified. You may elect to have the incidents auto resolve after 10 minutes. In our Java script
below we also set the severity to “info” so that the alert gets tagged as a “low priority”
notification. More information on Custom Event Transformer can be found here:
- Select “edit integration” to modify the provided default java script provided. Replace the existing js example with the following code (cut and paste the following segment):
var body = PD.inputRequest.body;
var twitter_description = String(PD.inputRequest.body.description);
var cef_event_deploy = {
event_type: ‘cef’,
event_action: PD.Trigger,
summary: twitter_description,
description: twitter_description,
message: body.description,
client_url: ‘https://twitter.com/’,
client: ‘Twitter’,
source_origin: ‘Twitter via Tweepy API’,
severity: ‘info’,
event_class: ‘tweet’
};
PD.emitCEFEvents([cef_event_deploy]);
- Save your changes and copy to your clipboard the integration key.
PART 2: TWEEPY SETUP:
- We have tested this approach on two types of servers. One was a local CentOS VM
running off of a Macbook pro via the VirtualBox. The other was an AMI instance off of AWS
running Ubuntu. You can select whichever system is more appropriate for you.
Ensure you have a python environment available in order to execute the code below
Download and install the PagerDuty agent. The PagerDuty agent is needed to send the
information over to pagerduty via the ‘pd-send’ command line utility. Details and Instructions for
installing the pdagent API are located here:
- Download and install the tweepy API.
Here are instructions for getting it for a CentOS distro:
- Modify the tweepy code lines 11,12,13,14 to use the twitter API tokens from your
twitter developer account. Also change the “YOUR_PD_API_Key” in the code below with your
key captured from Part 1, step 4 above. Notice line 15 “keywords” contains the twitter “string” to
listen for (ie. “pagerduty”). Make your modifications and save the file as tweepypd.py
- We now need to start a terminal session and run your modified script. At the command line type: python ./tweepypd.py
#!/usr/bin/python
# Import the necessary package to process data in JSON format
try:
import json
except ImportError:
import simplejson as json
# Import the tweepy library
import tweepy
import os
# Put keywords that you want to filter into an array.
#
keywords = [‘pagerduty’]
# Variables that contains the user credentials to access Twitter API
ACCESS_TOKEN = ‘<YOUR_TWITTER_API_DEV_TOKENS>’
ACCESS_SECRET = ‘<YOUR_TWITTER_API_DEV_TOKENS>’
CONSUMER_KEY = ‘<YOUR_TWITTER_API_DEV_TOKENS>’
CONSUMER_SECRET = ‘<YOUR_TWITTER_API_DEV_TOKENS>’
# Setup tweepy to authenticate with Twitter credentials:
auth = tweepy.OAuthHandler(CONSUMER_KEY, CONSUMER_SECRET)
auth.set_access_token(ACCESS_TOKEN, ACCESS_SECRET)
# Create the api to connect to twitter with your credentials
api = tweepy.API(auth, wait_on_rate_limit=True, wait_on_rate_limit_notify=True, compression=True)
class StreamListener(tweepy.StreamListener):
def on_status(self, status):
status_var = “”" + status.text + “”"
os.system(‘pd-send -k <YOUR_PD_API_KEY> -t trigger -d “”’ + status_var.encode(“utf-8”) + ‘""’)
def on_error(self, status_code):
if status_code == 420:
return False
stream_listener = StreamListener()
stream = tweepy.Stream(auth=api.auth, listener=stream_listener)
stream.filter(track=keywords)
PART 3: GENERATING THE INCIDENT
You can wait for a PagerDuty incident to be created when a tweet containing your “keyword” shows up or you can login to your twitter account and post a tweet with the “keyword” that you would like to trigger on (ie. “pagerduty” in our example).
The PagerDuty twitter service will receive and surface an incident. It will also create a “t” marker in the visibility infrastructure health console, indicating a tweet with the “keyword” was
captured.Conclusion:
Disruptive organizations are leveraging sentiment analysis and can use PagerDuty to quickly recover from negative tweets, ensuring customer loyalty and helping reduce churn risk.
Posts: 1
Participants: 1
@benyitzhaki wrote:
Hi there,
I have created an integration to pagerduty using an API Key and was hoping to be able to get some basic information regrading the account using it (for example, the sub domain or if the key has full-access).Also, when creating web hooks, it’s would be super comfortable to be able to subscribe to all services instead to just one of them.
thanks
Posts: 1
Participants: 1
@poojaHarness wrote:
I tried to fire a pager duty event.
api endpoint: https://events.pagerduty.com/v2/enqueue
payload:
{
“routing_key”: “d3a4e02ee8e846b49b58b19e54068a0Z”,
“event_action”: “trigger”,
“payload”: {
“summary”: “test”,
“severity”: “info”,
“source”: “test”,
“timestamp”: “2015-07-17T08:42:58.315+0000”
}
}If you see here, the routing key is not a valid hexadecimal, so I was expecting the api to throw an error, but it returns with success
{
“status”: “success”,
“message”: “Event processed”,
“dedup_key”: “df6bdc65402f4a5fb4407ba2ee052a61”
}with an invalid key, where is the event being processed and its associated with which service.
Also, there should be validation if the routing key is a valid hexadecimal but is not linked to any existing service in Pager duty.
Posts: 1
Participants: 1
@bcooper wrote:
Hello!
I’m using the PagerDuty app for Splunk and sending events to the global queue for routing & deduplication.
I have configured global rules to extract the description & dedup_key fields from the event using a simple regex (.*). The description extraction works as I can see the summary name keep changing. The dedup_key extraction however doesn’t appear to work and as a result all alerts are being attached to a single incident because the default dedup_key is the Splunk search name.
Posts: 1
Participants: 1
@sutirtha1234 wrote:
I have a script that reads logs. It can connect to Pagerduty via API call( or through Prometheus alertmanager or any other service that you recommend).
I need to assign the person on the log as a responder in PagerDuty. This has to be done via code and not UI.
What should i use at the PagerDuty end to achieve this? An API call? Custom Event Transformer? etc.
Posts: 1
Participants: 1
@GagandeepSingh wrote:
I want to assign tags to users using the rest api available from pd. I went through the api reference docs but was unable to find a way that would allow me to modify a user and add tags to it. Just wanted to check if this is even possible using api or not. If its possible , then a solution will be highly appreciated.
Posts: 1
Participants: 1
@neilconlan wrote:
Is there a way to know when a user was created from the /user api or any other api (indirectly?).
I am looking for a way to delete inactive users that where created over X days ago. Is this possible?
Posts: 2
Participants: 1
@jon wrote:
Hello PD community!
I’m Jon, and I’m a developer at PagerDuty. I joined in 2016, and worked in Toronto until 2019, when I moved to working remotely from Vancouver. I’ve worked on many of our features, including timeline entries, Modern Incident Response, and Visibility. I’m also one of PagerDuty’s Incident Commanders.
Prior to PagerDuty, I worked for several companies, all of whose names started with A, but I can say that working for PD is A++
Posts: 1
Participants: 1
@antoncohen-crux wrote:
When creating a user via the API, the ‘role’ attribute must be one of (from the error message):
Role must be in read_only_user, owner, admin, user, observer, limited_user, team_responder, or restricted_access.
If ‘team_responder’ is picked, the user is created with a base role of ‘observer’. When that user is added to a team they have the team role of ‘observer’.
The ‘role’ attribute does work correctly when setting the role to ‘user’ (aka manager).
Example code:
import json import os import pypd user_data = { "type": "user", "name": "New User", "email": "new@example.com", "role": "team_responder", } print("User to create:") print(json.dumps(user_data, indent=2, sort_keys=True)) user = pypd.User.create( data=user_data, from_email="me@example.com", api_key=os.environ["PAGERDUTY_API_KEY"], ) print("\nUser created:") print(json.dumps(user.json, indent=2, sort_keys=True))I’ve tried it with the Python and Go libraries, same behavior.
How do I create users with the role of ‘team_responder’ or ‘responder’[1] via the API?
[1] ‘responder’ isn’t accepted by API when creating a user.
Posts: 2
Participants: 1
@sutirtha1234 wrote:
The visibility docs https://support.pagerduty.com/docs/visibility-console have some examples with emitCEFEvents object. I can’t see any documentation of it. Is there some library where i can look up allowed elements?
Posts: 1
Participants: 1
