# Alert on non-reporting beats
**URL:** https://discuss.elastic.co/t/alert-on-non-reporting-beats/140046
**Category:** Beats
**Created:** [July 15, 2018, 3:53am UTC](https://discuss.elastic.co/t/alert-on-non-reporting-beats/140046 "2018-07-15T03:53:10Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Sanjeev\_Gopal](https://discuss.elastic.co/u/Sanjeev_Gopal)
#### Post date: [July 15, 2018, 3:53am UTC](https://discuss.elastic.co/t/alert-on-non-reporting-beats/140046/1 "2018-07-15T03:53:11Z")
How can I setup an alert for a non-reporting beat? In other/specific words, I need to know, ideally through Kibana, when any of the beats stops sending data. I know I can setup monitoring on the data received, but here I want to know as soon as I stop receiving data.
---
### Author:  [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [July 17, 2018, 6:46am UTC](https://discuss.elastic.co/t/alert-on-non-reporting-beats/140046/2 "2018-07-17T06:46:59Z")
I'm thinking you could create a query that checks for the documents from the Beat. An if the query does return 0 results for the last minute, you trigger an alert.
---
### Author:  [@Sanjeev\_Gopal](https://discuss.elastic.co/u/Sanjeev_Gopal)
#### Post date: [July 31, 2018, 9:26am UTC](https://discuss.elastic.co/t/alert-on-non-reporting-beats/140046/3 "2018-07-31T09:26:58Z")
I'll soon have over a 1000 beats. So I can't really write a query for every beat, and if I write a single query, I woudn't know which beat stopped responding, right?
What I have settled for now, is to enable the HTTP Endpoint on the beats. I then use Heartbeat to check the port. It of course doesn't tell me that the beats are surely sending metrics, but just that they're running.
@ruflin - Please can you comment on my approach? Also, is it possible for me to write a query to list all reporting beats every 30 minutes, and highlight what is missing comparing to the earlier list?
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [July 31, 2018, 8:40pm UTC](https://discuss.elastic.co/t/alert-on-non-reporting-beats/140046/4 "2018-07-31T20:40:56Z")
@Sanjeev, One idea, you could perform a terms aggregation aggregating one bucket per beat, and check that against a list of expected beats. Would that solve your problem? You must have a master list of beats somewhere that you expect to exist right?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 28, 2018, 10:40pm UTC](https://discuss.elastic.co/t/alert-on-non-reporting-beats/140046/5 "2018-08-28T22:40:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.