# Auditbeat not logging started process that run very short

**URL:** <https://discuss.elastic.co/t/auditbeat-not-logging-started-process-that-run-very-short/255877>\
**Category:** SIEM\
**Created:** [November 18, 2020, 5:13pm UTC](https://discuss.elastic.co/t/auditbeat-not-logging-started-process-that-run-very-short/255877 "2020-11-18T17:13:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bertr](https://avatars.discourse-cdn.com/v4/letter/b/e495f1/32.png) [@bertr](https://discuss.elastic.co/u/bertr)\
**Post date:** [November 18, 2020, 5:13pm UTC](https://discuss.elastic.co/t/auditbeat-not-logging-started-process-that-run-very-short/255877/1 "2020-11-18T17:13:44Z")

</div>

The process dataset of the system module of auditbeat does not register short running processes. (version = 7.8.1). E.g. cat of small file will not show up in auditbeat index, cat of a bigger file will. Both cat's do show up in auditd when running aureport -f | grep cat.  
This is quite annoying for SIEM. E.g. the shred detector will not be triggered when used for small files. In auditbeat.yml period = 1s.

---

<div class="post-metadata">

**Author:** ![bertr](https://avatars.discourse-cdn.com/v4/letter/b/e495f1/32.png) [@bertr](https://discuss.elastic.co/u/bertr)\
**Post date:** [November 29, 2020, 1:42pm UTC](https://discuss.elastic.co/t/auditbeat-not-logging-started-process-that-run-very-short/255877/2 "2020-11-29T13:42:55Z")

</div>

I found the issue: auditd was active on the system(s).

---

<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:** [December 27, 2020, 3:42pm UTC](https://discuss.elastic.co/t/auditbeat-not-logging-started-process-that-run-very-short/255877/3 "2020-12-27T15:42:56Z")

</div>

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