All Apps and Add-ons

[Splunk App for CEF] cefout does not forward data with stats command

sylim_splunk
Splunk Employee
Splunk Employee

We have a CEF output that isn't sending events via the cefout command. We can take the scheduled search and just remove the end with the |cefout and CEF events are generated.

<Datamodel search>
| stats ...
|cefout ...

For some unknown reason they don't get sent when the cefout command is included.

If we use only the first query before stats command, it works and sends events with the |cefout. Adding in the | stats and subsequent lines causes it to not send events.

Labels (1)
1 Solution

sylim_splunk
Splunk Employee
Splunk Employee

The behavior is expected and stats before cefout is not supported. The cefout command is supposed to work on the indexer layer , which is explained in the doc,  https://docs.splunk.com/Documentation/CEFapp/2.3.0/DeployCEFapp/Howtheappworks

 The reason is because the stats command is supposed to run on SH after prestats on indexers but cefout has to run on indexers -  putting stats before cefout causes the search results to pass back to the SH and never come back to indexers. When the search processing moves to the search head, it cannot move back to the indexer.

View solution in original post

sylim_splunk
Splunk Employee
Splunk Employee

The behavior is expected and stats before cefout is not supported. The cefout command is supposed to work on the indexer layer , which is explained in the doc,  https://docs.splunk.com/Documentation/CEFapp/2.3.0/DeployCEFapp/Howtheappworks

 The reason is because the stats command is supposed to run on SH after prestats on indexers but cefout has to run on indexers -  putting stats before cefout causes the search results to pass back to the SH and never come back to indexers. When the search processing moves to the search head, it cannot move back to the indexer.

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!

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 ...

Data Persistence in the OpenTelemetry Collector

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

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...