hi mahesh_ravji,
This examples routes events of windows_snare_log source type to the appropriate index based on their log types. "Application" logs will go to an alternate index, while all other log types, such as "Security" , will go to the default index.
To make this determination, it uses props.conf to direct events of windows_snare_log source type through the transforms.conf stanza named "AppRedirect" , where a regex then looks for the log type, "Application" . Any event with a match on "Application" in the appropriate location is routed to the alternate index, "applogindex" . All other events go to the default index.
Edit props.conf
Add this stanza to $SPLUNK_HOME/etc/system/local/props.conf:
[windows_snare_syslog]
TRANSFORMS-index = AppRedirect
This directs events of windows_snare_syslog sourcetype to the AppRedirect stanza in transforms.conf
Edit transforms.conf
Add this stanza to $SPLUNK_HOME/etc/system/local/transforms.conf:
[AppRedirect]
REGEX = MSWinEventLog\s+\d+\s+Application
DEST_KEY = _MetaData:Index
FORMAT = applogindex
This stanza processes the events directed here by props.conf . Events that match the regex (because they contain the string "Application" in the specified location) get routed to the alternate index, "applogindex" . All other events route as usual to the default index.
try to use this example.
For more informations, follow this link:
http://docs.splunk.com/Documentation/Splunk/6.3.2/Indexer/Setupmultipleindexes
and read paragraph **Route specific events to a different index **
... View more