# Auditd rules to save terminal output

**URL:** <https://discuss.elastic.co/t/auditd-rules-to-save-terminal-output/240930>\
**Category:** Beats\
**Tags:** auditbeat\
**Created:** [July 13, 2020, 9:03am UTC](https://discuss.elastic.co/t/auditd-rules-to-save-terminal-output/240930 "2020-07-13T09:03:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matt\_Rollo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matt_rollo/32/48133_2.png) [@Matt\_Rollo](https://discuss.elastic.co/u/Matt_Rollo)\
**Post date:** [July 13, 2020, 9:03am UTC](https://discuss.elastic.co/t/auditd-rules-to-save-terminal-output/240930/1 "2020-07-13T09:03:29Z")

</div>

Thanks to autidbeat I'm able to logging on ELK command execution with flags, but I also need to save output from terminal of that command call. Is there any way to do that by auditbeat ? Maybe some rules to record kernel file descriptor ?

Cheers  
R

---

<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:** [August 10, 2020, 11:18am UTC](https://discuss.elastic.co/t/auditd-rules-to-save-terminal-output/240930/2 "2020-08-10T11:18:33Z")

</div>

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