# System module not logging severity & facility

**URL:** <https://discuss.elastic.co/t/system-module-not-logging-severity-facility/195171>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [August 14, 2019, 9:41am UTC](https://discuss.elastic.co/t/system-module-not-logging-severity-facility/195171 "2019-08-14T09:41:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hrak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hrak/32/34222_2.png) [@hrak](https://discuss.elastic.co/u/hrak)\
**Post date:** [August 14, 2019, 9:41am UTC](https://discuss.elastic.co/t/system-module-not-logging-severity-facility/195171/1 "2019-08-14T09:41:13Z")

</div>

Judging from the ingest pipeline definition of the Filebeat system module, it currently does not support logging of the severity and facility of an event, even if you adapt your syslog daemon configuration to log these in the log file.

Being able to filter on events greater than a certain severity level is obviously a very useful feature for central logging. Is there any way to get this to work currently, or are there any plans in the near future to support this?

---

<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:** [September 11, 2019, 9:53am UTC](https://discuss.elastic.co/t/system-module-not-logging-severity-facility/195171/2 "2019-09-11T09:53:09Z")

</div>

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