# Incident management with ServiceNow and Elasticsearch

**URL:** <https://discuss.elastic.co/t/incident-management-with-servicenow-and-elasticsearch/278579>\
**Category:** Elasticsearch\
**Created:** [July 13, 2021, 4:39pm UTC](https://discuss.elastic.co/t/incident-management-with-servicenow-and-elasticsearch/278579 "2021-07-13T16:39:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rajsolanki](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rajsolanki/32/86859_2.png) [@rajsolanki](https://discuss.elastic.co/u/rajsolanki)\
**Post date:** [July 13, 2021, 4:39pm UTC](https://discuss.elastic.co/t/incident-management-with-servicenow-and-elasticsearch/278579/1 "2021-07-13T16:39:40Z")

</div>

I have followed [part 1](https://www.elastic.co/blog/how-to-connect-servicenow-and-elasticsearch-for-bidirectional-communication) and [part 2](https://www.elastic.co/blog/how-to-perform-incident-management-with-servicenow-and-elasticsearch) Everything works great. Only minor issue is its creating duplicate incidents. If i put throttle period then if some other app has status down , it wont trigger an incident ☹

if there any logic i can change in watcher which would to skip generating duplicate incidents for same app ?

if also tried

```auto
if (state == 'Resolved' || state == 'Closed' || state == 'Canceled' || state !== 'New') {
appsNeedingTicket.add(app.key);
}

```

---

<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:** [August 10, 2021, 4:40pm UTC](https://discuss.elastic.co/t/incident-management-with-servicenow-and-elasticsearch/278579/2 "2021-08-10T16:40:15Z")

</div>

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