# Testing filebeat **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [April 10, 2019, 6:36am UTC](https://discuss.elastic.co/t/testing-filebeat/176145 "2019-04-10T06:36:44Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![furstenheim-geoblink](https://avatars.discourse-cdn.com/v4/letter/f/a5b964/32.png) [@furstenheim-geoblink](https://discuss.elastic.co/u/furstenheim-geoblink)\ **Post date:** [April 10, 2019, 6:36am UTC](https://discuss.elastic.co/t/testing-filebeat/176145/1 "2019-04-10T06:36:45Z")
Hi, I'd like to know how to test a filebeat configuration. I have filebeat installed locally, so I can do `filebeat test config -c $MY_FILE`. That is good to test if the configuration is semantically correct. However, I'd like to test that the configuration rules are as I want. Something like: `filebeat test match -c $MY_FILE -i FILE_TO_TEST` and output could be all lines that have passed, for example. Alternatively, something like: `filebeat test match -c $MY_FILE -i FILE_TO_TEST -i $MY_STRING` Thanks ---
**Author:** ![BKG](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bkg/32/43591_2.png) [@BKG](https://discuss.elastic.co/u/BKG)\ **Post date:** [April 11, 2019, 2:18pm UTC](https://discuss.elastic.co/t/testing-filebeat/176145/2 "2019-04-11T14:18:53Z")
You could probably do something with [filebeat stdin input](https://www.elastic.co/guide/en/beats/filebeat/master/filebeat-input-stdin.html), but you would need to develop it as the command doesn't have this feature. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 9, 2019, 2:18pm UTC](https://discuss.elastic.co/t/testing-filebeat/176145/3 "2019-05-09T14:18:56Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.