Getting Data In

Why are Windows event logs with MSSQLSERVER$AUDIT as source getting truncated and the message is empty?

gregory_cordier
Explorer

Hi,

We have an auditing setup which logs in Windows event logs (Forwarded Events) as "MSSQLSERVER$AUDIT" source.
they are well displayed in event viewer console, but the log is truncated and message is empty :

alt text

here the input file on windows server :
alt text

on the other side "Microsoft Windows Security auditing" events that are in "Forwarded Events" too are correctly sent and parsed in Splunk Indexer.

how come ?
where elsewhere do I have to check ?

Splunk UF is installed on Windows server with the Windows Events Collector

Thanks

0 Karma
1 Solution

gregory_cordier
Explorer

After searching and get helped from support, I tried the solution described in https://answers.splunk.com/answers/326943/why-is-windows-event-log-message-data-being-trunca.html

now logs are fully sent and parsed.

View solution in original post

0 Karma

gregory_cordier
Explorer

After searching and get helped from support, I tried the solution described in https://answers.splunk.com/answers/326943/why-is-windows-event-log-message-data-being-trunca.html

now logs are fully sent and parsed.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

@gregory.cordier If your problem is resolved, please accept the answer to help future readers.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...