# Kibana Watcher - Pagerduty Connection Issue

**URL:** <https://discuss.elastic.co/t/kibana-watcher-pagerduty-connection-issue/223455>\
**Category:** Kibana\
**Created:** [March 13, 2020, 7:03am UTC](https://discuss.elastic.co/t/kibana-watcher-pagerduty-connection-issue/223455 "2020-03-13T07:03:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rj23495](https://avatars.discourse-cdn.com/v4/letter/r/7ba0ec/32.png) [@rj23495](https://discuss.elastic.co/u/rj23495)\
**Post date:** [March 13, 2020, 7:03am UTC](https://discuss.elastic.co/t/kibana-watcher-pagerduty-connection-issue/223455/1 "2020-03-13T07:03:09Z")

</div>

Lets say, I am using Watcher in ELK stack and there are 2 network interfaces in ELK- one for elasticsearch and other one for kibana, so when watcher triggers an alert in pagerduty, which network interface does it use - kibana or elasticsearch?

---

<div class="post-metadata">

**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\
**Post date:** [March 13, 2020, 8:30am UTC](https://discuss.elastic.co/t/kibana-watcher-pagerduty-connection-issue/223455/2 "2020-03-13T08:30:54Z")

</div>

Watcher is an Elasticsearch feature, Kibana is just configuring it from the outside like any other client.

So when a watcher is executed, it will use the Elasticsearch infrastructure, not the Kibana one.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 10, 2020, 8:31am UTC](https://discuss.elastic.co/t/kibana-watcher-pagerduty-connection-issue/223455/3 "2020-04-10T08:31:09Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.