10333 is the tracking issue for this (and some other related) problems. I am currently working on a fix for the ingest pipeline for this integration. In the long term, I plan on bringing in the full go parser from https://github.com/elastic/go-libaudit to ship pre-parsed audit logs directly from the beat.
Integration Name
Auditd Logs [auditd]
Dataset Name
auditd.log
Integration Version
3.20.0
Agent Version
8.15.0
Agent Output Type
elasticsearch
Elasticsearch Version
8.15.0
OS Version and Architecture
Linux
Software/API Version
No response
Error Message
No response
Event Original
No response
What did you do?
default configuration
What did you see?
The following auditd message is not being properly parsed.
results in
What did you expect to see?
Expected:
Anything else?
No response