# Getting kernel messages directly ala dmesg (no filesystem)? **URL:** \ **Category:** Beats\ **Created:** [July 26, 2016, 8:58pm UTC](https://discuss.elastic.co/t/getting-kernel-messages-directly-ala-dmesg-no-filesystem/56448 "2016-07-26T20:58:01Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![eldondev](https://avatars.discourse-cdn.com/v4/letter/e/d26b3c/32.png) [@eldondev](https://discuss.elastic.co/u/eldondev)\ **Post date:** [July 26, 2016, 8:58pm UTC](https://discuss.elastic.co/t/getting-kernel-messages-directly-ala-dmesg-no-filesystem/56448/1 "2016-07-26T20:58:02Z")
Is there a way to use beats to get kernel messages directly from the kernel? I am experiencing some filesystem errors, and I am not sure how to get that info back with a file or metric beat if nothing can write the error to disk. ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [July 26, 2016, 9:45pm UTC](https://discuss.elastic.co/t/getting-kernel-messages-directly-ala-dmesg-no-filesystem/56448/2 "2016-07-26T21:45:58Z")
I wonder if you could read `/proc/kmsg` from Filebeat. Disclaimer: I've never tried this. Or another option might be to pipe `dmesg` through Filebeat using stdin (`dmesg -w | filebeat -c filebeat.yml`). You would have to configure a prospector to read from stdin. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 16, 2016, 8:58pm UTC](https://discuss.elastic.co/t/getting-kernel-messages-directly-ala-dmesg-no-filesystem/56448/3 "2016-08-16T20:58:03Z")
This topic was automatically closed after 21 days. New replies are no longer allowed.