Splunk Enterprise Security

Splunk Enterprise Security: Logs not being displayed on search head unless index name is specified explicitly

deepakgaonkar
Explorer

Hi All,

I've seen an issue where a particular string is searched, the search head displays only the logs which are indexed under os and not all the logs. To search for a specific log file we had to mention the index name under which it was being logged.
Ideally, Splunk should have searched for all the occurrences where the log is present and shown all the source_types.

exp: Searched for abc* (without mentioning any index name) -> this would show only under the index os .
But abc_log is also indexed explicitly under os_abc index .
if searched explicitly index=os_abc the expected logs are displayed

0 Karma
1 Solution

Vijeta
Influencer

@deepakgaonkar These settings are specified for each role under authorize.conf. The srchIndexesDefault parameter is set to os in you case so whenever you do not specify any index it only searches in the default index assigned to your role which is os in your case. Try using index=* abc* you will find the string, but index=* is not recommended as it will search all the indexes for the string match. Is better to be precise with the index names if you know them.

View solution in original post

0 Karma

Vijeta
Influencer

@deepakgaonkar These settings are specified for each role under authorize.conf. The srchIndexesDefault parameter is set to os in you case so whenever you do not specify any index it only searches in the default index assigned to your role which is os in your case. Try using index=* abc* you will find the string, but index=* is not recommended as it will search all the indexes for the string match. Is better to be precise with the index names if you know them.

0 Karma

deepakgaonkar
Explorer

@Vijeta , Many thanks for the response . Its just that unless you know under which index name the log or text is defined , it would misguide . In my case when i searched for abc and searched it did not show the sourcetype or the source i was looking for , which made me assume that it is not being logged. Later when i checked the DS and then the UF's input.conf i understood its being logged but under different index name .
Completely agree with you to refine and better searching index name should be specified .
Many thanks for your help again !

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.


Introducing Unified TDIR with the New Enterprise Security 8.2

Read the blog

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...