Splunk Search

Generating custom command not streaming output

jakubzak
Explorer

I have created following custom command:

@Configuration(streaming=True)
class GenerateTextCommand(GeneratingCommand):

  count = Option(require=True, validate=validators.Integer(0))
  text = Option(require=True)

  def generate(self):
    for i in range(1, self.count + 1):
       sleep(5)
       yield {'id': i, '_time': time.time(), '_raw': unicode(i) + '. ' + self.text}

dispatch(GenerateTextCommand, sys.argv, sys.stdin, sys.stdout, __name__)

and I have prepared configuration in commands.conf:

[teststream]
filename = testStream.py
chunked = true

My expectation is that if I execute this command in Search command line in Splunk UI:

| teststream count=4 text="asdf"

It will print out each 5 seconds asdf text 4 times. Instead of it it generates 4 events and prints it after 20 seconds. Timestamps shows that generation time is strictly by "my rules" - new message each 5 seconds.

Is my understanding of "output streaming" from custom command incorrect or am I doing something wrong?

Thanks for help

Jakub

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...