"splunk add oneshot" not working

[vpsmax]

Hello.

Trying to test a sourcetype using "oneshot".  Although we were able to add raw data using "oneshot" the first time, we are not seeing any subsequent updates.  The command we are using is ...

splunk add oneshot /tmp/<filename>.txt -index <indexname> -sourcetype <sourcetypename>

What are the best approaches to troubleshoot "oneshot"?

Regards,
Max

[anwarmian]

We need to remember that Universal Forward does not do index-time parsing, on the other hand a Splunk Enterprise server such as a Heavy Forwarder, Search Head, Deployment server, depoyer, etc does the index-time parsing.  Indexers  expect that the data that come via another Splunk Enterprise server have the data cooked.

[ivanreis]

Hi Max, use this command to check if the file status of the file has been reset

splunk cmd btprobe -d $SPLUNK_DB/fishbucket/splunk_private_db --file <file> --reset

The response from this command is an indicator that the status for the file has been reset. Again, a restart of the forwarder is required for Splunk to then ingest that file anew.

if this assist you, please upvote. 

[bdiego_splunk]

Hi Max,

Please try:

splunk add oneshot -source /tmp/<filename>.txt -index <indexname> -sourcetype <sourcetypename>

Regards,

-bd-