# FileBeat debugging and error monitoring

**URL:** <https://discuss.elastic.co/t/filebeat-debugging-and-error-monitoring/169499>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 21, 2019, 10:53pm UTC](https://discuss.elastic.co/t/filebeat-debugging-and-error-monitoring/169499 "2019-02-21T22:53:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chitraj8](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chitraj8/32/42639_2.png) [@chitraj8](https://discuss.elastic.co/u/chitraj8)\
**Post date:** [February 21, 2019, 10:53pm UTC](https://discuss.elastic.co/t/filebeat-debugging-and-error-monitoring/169499/1 "2019-02-21T22:53:31Z")

</div>

I am using Filebeat 6.6.1 version and using kafka output with multiple topics.  
I am beginner to use filebeats trying to read through documentation and do stuff as per the requirement.  
I do know there is a X-pack monitoring pack that can be added across ELK stack to get better monitoring views and alerts.

We would like to configure some alerts with our internal monitoring system to check on below things when it occurs with filebeat:  
a. kafka cluster is not being reached  
b. kafka topic is not available to write data

An api to monitor list of filebeat things will help us to make the metric pipeline better.

---

<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:** [March 21, 2019, 10:53pm UTC](https://discuss.elastic.co/t/filebeat-debugging-and-error-monitoring/169499/2 "2019-03-21T22:53:33Z")

</div>

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