@hari.u wrote:
We would like to add notifications to our manager also on weekly on-call changes. Currently on-call person is only receiving it and it will be good if we can add team DL in it.
This feature is not there in current pager duty tool
Posts: 2
Participants: 1
@himmel92 wrote:
Billing alerts in Google Cloud Platform can be assigned a topic from Pub/Sub. From what I can tell, the only Pub/Sub topic subscription option is to push to an “Endpoint URL”. PD doesn’t appear to have an integration for this – am I missing something?
Posts: 2
Participants: 1
@EvgeniyKulyk wrote:
Hi guys, i have a question regarding integrations
We have a prometheus, monitoring endpoint on the web,
When endpoint is not reachable, it creates an incident in PagerDuty, with no Priority set in it
PagerDuty crates a ticket in Jira Server,But no priority is set in JIra ticket either
but we need the priority to be P1 - Highest in jira ticket
How can we achieve this ?
Thanks in advance,
Evgeniy
Posts: 2
Participants: 1
@EvgeniyKulyk wrote:
Hi guys,
I have a question regarding automatic resolution of am incident:
Prometheus integration created an incident in PageDuty,
People were assigned to an incident
Than after some time, Prometheus integration resolved the incident,
But no notification was sent to anybody that an incident was closedHow can we fix this ?
Can we configure somehow to send a notification to assignee and subscribers, that issue were resolved ?Thanks,
Evgeniy
Posts: 3
Participants: 2
@EvgeniyKulyk wrote:
Hi guys,
We have a case when JIRA ticket is created using PagerDuty integration with JIRA and Prometheus,
Problem is when for example,
- Prometheus created incident in PagerDuty
- PagerDuty created ticket in JIRA with status Open
- PagerDuty changes status of the ticket to Assigned
- 3 minutes later, before anyone acknowledged the incident, Prometheus resolves an incident
Ticket stays in Assigned status instead of being transferred to Completed,
We have a status mapped - Acknowledged - In Progress - for Jira to PagerDutyBy Jira Workflow, it is not allowed to transfer from Assigned to Completed
Can we suppress Jira flow somehow to set Status to completed whenever Incident is Resolved ?
Thanks,
Evgeniy
Posts: 1
Participants: 1
@dferdinand wrote:
We had an issue where teams would never look at pagerduty and rely on grafana for everything. so i hacked together an integration that would display alerts and key info on grafana for teams.
Please have a look here, any feedback would be great!
(I’m new to open source and developing so its all great for learning!)David
Posts: 3
Participants: 2
@Punnada wrote:
I have set schedule online support via phone on Call L1, L2, L3
but have some problem when I have alert but not call to L1 then wait a 15mins will raise to L2 support and have to call in normally.
In timeline log show Call L1 not response then call to L2.
I already test to reassign to Call L1 can call normallyPls help to check? how can I verify?
Posts: 2
Participants: 1
@JoshDadswell wrote:
I am having trouble with alerts triggering from emails not correctly rendering the email body see below:
Posts: 2
Participants: 1
@rgatchalianjr wrote:
I recently joined Pager Duty as a Renewal Specialist based in our HQ in beautiful San Francisco.
Before joining PagerDuty, I was part of the renewals team at Prysm, Inc.
I was born in Manila, lived in Seattle, and most of my life in San Francisco Bay Area. I love to travel and eat good food.
Best,
Romeo
Posts: 1
Participants: 1
@JohnFranklin wrote:
Any plans to enable required values on manual resolution of an incident? We’d like to make it so all manually resolved incident require a resolution note to be entered.
Thanks.
Posts: 1
Participants: 1
@shiller wrote:
Greetings! I’m Sean and recently started as a renewals specialist in the San Francisco office. I’m from San Francisco originally but I’ve lived all over the country, including Denver and western Washington.
Before PagerDuty, I worked for Sungage Financial as a solar finance specialist.
I work on electronic music in my free time and frequent the Goodwill outlet in Oakland.
Posts: 1
Participants: 1
@DG wrote:
I’m trying to create automatically create a jira ticket from pager duty and the Component field doesn’t seem to be available. I’ve looked through all of the custom fields and it’s not in the list. Otherwise I can create a jira ticket but for this alert a Component is required. Appreciate any help anyone can provide.
Posts: 1
Participants: 1
@preet wrote:
I accidentally signed up for my corporate invitation using my personal email address. Though this doesn’t affect escalations, I need to fix this. Would anyone have any suggestions please?
I’m very new to the product so don’t know if this a user, corporate or support change.
Thanks
Preet
Posts: 1
Participants: 1
@Mworel wrote:
Hello!
I’m a solutions consultant with PagerDuty in SF, and I help you not only solve your on call issues, but also streamline your digital operations, saving time, money, and wear and tear on your staff!
Ask me about best practices, integrations, and design!
Posts: 1
Participants: 1
@EvgeniyKulyk wrote:
Hi guys,
From recently, couple of days, our Jira server to PagerDuty integration is not working properly
In pagerduty we have a messages:
Please upgrade the PagerDuty add-on
To use some features in the PagerDuty Jira Integration, the PagerDuty add-on in Jira needs to be updated. You can update the add-on from the Atlassian Marketpace .
But our addon is up to date - version 3.0.0
Does that mean that all our integrations currently are broken ???
How can we fix this?
Thanks,
Evgeniy
Posts: 3
Participants: 2
@PeteL_MIET wrote:
Just wanted to say HI.Am an App-V application packager (MSFT)
Posts: 2
Participants: 2
@dellis wrote:
Hello PagerDuty community! My name is David Ellis.
I’m originally from several small towns in central west Texas that you’ve likely never heard of. Prior to PagerDuty, I spent the last eight and a half years writing device and network provisioning software at Rackspace.
Outside of work I’m either spending time with the family or tinkering with a side project. The family and I like hiking, biking, scootering, playing … anything to use up the children’s energy. Project wise, I’ve got a language project that’s pretty neat - https://www.ablelang.org.
I look forward to meeting everyone!
Posts: 1
Participants: 1
@Bored_Panda wrote:
Good Afternoon,
Very new to PagerDuty so still getting my feet wet, I have been asked to put together an integration between our ServiceNow instance and PagerDuty with 2 Way communications.
I have followed the integration guide which got me a fair ways in, I created a new Service using
“Events API v2” as the " Integration Type" which is using the Escalation Policy I created, this is emailing our dev instance ok and logging an incident as a Guest.I now want to get my 2 tickets talking to each other, the YouTube channel for PagerDuty is years out of date when watching the integration video, hope this gets updated soon, where would be the best place to look\start?
I have also noticed my PagerDuty Priorities are not refreshing, I have nothing showing in the impact, urgency or priority drop downs, I did go to configuration -> Incident Priority Settings and enable them, all connections are returning 200 status.
This is my first integration so currently circling the deep end of the pool… minus the sharks.
Posts: 4
Participants: 2
@demitri wrote:
One might encounter the following error:
AADSTS750: Authentication method “WindowsIntegrated, MultiFactor” by which the user authenticated with the service doesn’t match requested authentication method “Password, ProtectedTransport”
Our Azure SSO Integration Guide (under FAQ) has an in-depth technical description of why this occurs. Understanding the underlying mechanics of this, so that we could come up with an adequate explanation, took some reading into the SAML 2.0 Protocol Core Specification as well as the Azure SAML Protocol documentation. However, I must confess, when I went back to read what I had helped write way back then, it actually took me a few read-throughs to understand the underlying meaning.
So, this time around, I thought I’d have a bit of fun coming up with a more illustrative description of how it all happens. For the layperson, it may help to imagine the following brief dialogue that transpires, which leads to the error message:
User: “I want to sign in. Take me to my identity provider (IDP).”
PD (to user): “Okay, take this note (authentication request) to your IDP, which is over this way.”
PD (note to IDP reads): “This person wants to sign in to me. Their authentication method must EXACTLY match the minimum one that I typically require - and this exactness is as you have demanded that I require of users. The minimum that I ask is that the identity provider make their users provide a password (one authentication factor) per what I say here in myRequestedAuthnContextelement.”
User’s web browser: “Here’s an authentication request. I haveWindowsIntegratedand want to use that to authenticate.”
AD: (reads note) “Okay user, you say want to sign in usingWindowsIntegrated? TOO BAD, THAT METHOD IS NOT ALLOWED! IT MUST BE A PASSWORD AND ONLY A PASSWORD.”
PD (aside): But wait a minute AD, you yourself don’t even supportWindowsIntegratedwhen specifying aRequestedAuthnContextelement per your documentation*! The only way I could get around this is by the footgun of not requesting a minimum of authentication requirements, thus permitting disastrously insecure SAML configurations wherein no authentication method is required by the identity provider!* Per the FAQ:
- PagerDuty includes the
RequestedAuthnContextelement to request that the identity provider use, at the bare minimum, password authentication to identify users.- Azure expects the service provider require an exact match between the authentication type provided with the one requested, whenever
RequestedAuthnContextis provided.- Azure only supports requesting
Passwordtype authentication when specifyingRequestedAuthnContext.Users can get around this issue by using a different web browser that does not attempt to authenticate with the identity provider via the
WindowsIntegratedauthentication method, and using password authentication to access their identity.
Posts: 2
Participants: 1
@Mahesh wrote:
Why do a customer need to agree on marking a incident into ‘Pending state’ and effectively put SLA clock on hold. Incident management tell to quickly resolve/provide workaround to the degraded service. It has become organisation culture to put a ticket on hold when you need other team to respond or when change or problem is invoked. When Customer has agreed a certain SLA then why do we not stick to the SLA and inturn are using pending state as trick to get more time without missing SLA.
Posts: 1
Participants: 1
