# Pagerduty connector
**URL:** https://discuss.elastic.co/t/pagerduty-connector/323244
**Category:** Kibana
**Tags:** elastic-stack-alerting
**Created:** [January 16, 2023, 11:29am UTC](https://discuss.elastic.co/t/pagerduty-connector/323244 "2023-01-16T11:29:38Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@AdityaKhajuria](https://discuss.elastic.co/u/AdityaKhajuria)
#### Post date: [January 16, 2023, 11:29am UTC](https://discuss.elastic.co/t/pagerduty-connector/323244/1 "2023-01-16T11:29:38Z")
Rules & Connectors
Hi team, im trying to integrate Pagerduty with Elasticsearch, so far i have created the Elastic-Alerts service in Pagerduty and have used all those credentials right here in Kibana connector, but when im trying to run the test its giving me error -
**Test failed to run**
**The following error was found:**
**error posting pagerduty event**
**Details:**
**getaddrinfo ENOTFOUND [events.pagerduty.com](http://events.pagerduty.com)**
and yes, I have allowed Kibana to connect to all hosts [\*] in my kibana.yml file.
Ref:
- [PagerDuty connector and action | Kibana Guide [8.6] | Elastic](https://www.elastic.co/guide/en/kibana/current/pagerduty-action-type.html)
- [Alerting and action settings in Kibana | Kibana Guide [8.6] | Elastic](https://www.elastic.co/guide/en/kibana/current/alert-action-settings-kb.html#general-alert-action-settings)
---
### Author:  [@Patrick\_Mueller](https://discuss.elastic.co/u/Patrick_Mueller)
#### Post date: [January 17, 2023, 12:57pm UTC](https://discuss.elastic.co/t/pagerduty-connector/323244/2 "2023-01-17T12:57:36Z")
That looks like a DNS error of some kind. Can you run a `curl -v https://events.pagerduty.com/` from the machine running Kibana.
Did you enter a value in the API URL for the connector? For most purposes, you can leave it empty.
---
### Author:  [@AdityaKhajuria](https://discuss.elastic.co/u/AdityaKhajuria)
#### Post date: [January 18, 2023, 2:38pm UTC](https://discuss.elastic.co/t/pagerduty-connector/323244/3 "2023-01-18T14:38:44Z")
Yes, I have entered [https://events.pagerduty.com/v2/enqueue](https://events.pagerduty.com/v2/enqueue) in API URL which I got while creating Pagerduty services, and even if i leave it empty it still shows error - **Details:**
**getaddrinfo ENOTFOUND [events.pagerduty.com](http://events.pagerduty.com/)**
---
### Author:  [@Patrick\_Mueller](https://discuss.elastic.co/u/Patrick_Mueller)
#### Post date: [January 19, 2023, 2:25pm UTC](https://discuss.elastic.co/t/pagerduty-connector/323244/4 "2023-01-19T14:25:20Z")
I would suggest leaving the URL field blank, just to make sure no typos are accidentally entered, since you seem to be using the default address.
As mentioned previously, this seems like a DNS error occurring, on the machine that is running Kibana. Can you log into the machine running Kibana, and run the following command. I expect it will fail, and hopefully provide some diagnostics for getting your DNS set up correctly.
```
curl -v https://events.pagerduty.com/
```
---
### Author:  [@AdityaKhajuria](https://discuss.elastic.co/u/AdityaKhajuria)
#### Post date: [January 25, 2023, 5:06am UTC](https://discuss.elastic.co/t/pagerduty-connector/323244/5 "2023-01-25T05:06:21Z")
Hi Patrick,
yea that was a DNS issue only, I configured it and now I'm able to run the connector even without passing the URL. Thanks!
---
### Author:  [@Patrick\_Mueller](https://discuss.elastic.co/u/Patrick_Mueller)
#### Post date: [January 25, 2023, 1:19pm UTC](https://discuss.elastic.co/t/pagerduty-connector/323244/6 "2023-01-25T13:19:57Z")
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 22, 2023, 1:20pm UTC](https://discuss.elastic.co/t/pagerduty-connector/323244/7 "2023-02-22T13:20:00Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.