Splunk Enterprise

is there a way to check if makeresults stored the events in index or not ?

jayjoshi64
Engager

I am searching like this in Splunk:

  | makeresults count=3 | eval _raw="demo event" | collect index=main sourcetype="sample"

It generates the events and also stores these 3 events in the index.

and then I searched this:

| makeresults count=3 | eval _raw="demo event" | collect index="randomindex" sourcetype="sample"

Here, "randomIndex" is not available in the Splunk instance, so it will not store the events, but it will show all 3 events anyway when the above search is fired. but still not stored anywhere.

I am trying same to do using REST API to search "makeresults" multiple times and store in the given index but there is no way to check whether the events has been stored successfully or not.

Is there a way to check whether the makeresults stored the event successfully or not.? using job properties or anything.?

Tags (1)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi
you have to create Index before use collect command (see https://docs.splunk.com/Documentation/Splunk/7.0.1/SearchReference/Collect ) so you're sure to find events in that index.

Bye.
Giuseppe

jayjoshi64
Engager

I have checked whether index is available in the Splunk Instance by checking if index's stanza is available in indexes.conf or not.

if there is error message in the response. create the Index by adding the stanza in the indexes.conf

to check and add stanza: check stanza by REST API

0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...