Skip to main content
Question

Jamf truncating logs before they hit Splunk. How to address?

  • Nov 19, 2026 7:27 PM UTC
  • 1 reply
  • 11 views

cthonus
Forum|alt.badge.img+2

We are having some issues with Jamf truncating telemetry logs before they hit Splunk. It seems to be at 25KB (which seems really big for a log?) but it is causing problems, our security monitoring team insists they are not able to properly monitor with this issue.

How are you handling it? Is there any way to make the logs less verbose? We were discussing using a tool like Vector or Cribl to help clean up the logs, as we have a different issue that this would also help resolve. Just need to know if this is a way to go about adjusting for the size of the logs as well, and if it is not what else we are able to do about it. I understand there is a reason for the limit but our security department will not budge on something this major and we would have to find an alternative sooner rather than later (we are in a pilot PoC phase currently)

1 reply

thebrucecarter
Forum|alt.badge.img+16

Yep, we had that issue on some of our more verbose scripting logs.  We asked for a configurable amount there, but didn’t hear anything else about it.