# Interesting Use Case - Down Stream Alerting

**URL:** <https://discuss.elastic.co/t/interesting-use-case-down-stream-alerting/292360>\
**Category:** Elastic Observability\
**Tags:** elastic-stack-alerting\
**Created:** [December 17, 2021, 8:26pm UTC](https://discuss.elastic.co/t/interesting-use-case-down-stream-alerting/292360 "2021-12-17T20:26:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tthiry](https://avatars.discourse-cdn.com/v4/letter/t/a4c791/32.png) [@tthiry](https://discuss.elastic.co/u/tthiry)\
**Post date:** [December 17, 2021, 8:26pm UTC](https://discuss.elastic.co/t/interesting-use-case-down-stream-alerting/292360/1 "2021-12-17T20:26:35Z")

</div>

Hello,

I am relatively new to Elasticsearch and I have an interesting alerting use case. Assume I have a router with a layer of switches behind it. That layer of switches has a layer behind it and so on until we get to either an access layer switch or perhaps a host. I am monitoring the availability of each device in that tree. Lets pretend it 200 devices. If the router goes down I don't want to get 200 system down" alerts. I only want 1 alert for the router and I know the other 199 devices will be unavailable.

Is it possible to build this scenario with the tools available to Elasticsearch or would I have to build that logic outside of Elasticsearch. I think they key would be to somehow build that upstream \<-\> downstream relationship. Any ideas on how I could do this?

Thanks,  
Tony

---

<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:** [November 4, 2022, 8:33am UTC](https://discuss.elastic.co/t/interesting-use-case-down-stream-alerting/292360/2 "2022-11-04T08:33:27Z")

</div>