Deployment Architecture

Searches with 6.2

pil321
Communicator

I installed 6.2 in a lab environment and I'm getting some weird results when I do searches.

I have 1 indexer and 1 search head. I added the search peer using this. I deployed a few apps to a couple of hosts using a deployment server. I can see the indexes populating.

But, when I go to the search app on the search head or the indexer, the "what to search" text in the middle of the page states "waiting for data...." (?)

If I do a search host=*, I get nothing. The only time I will see anything is if I do a search by index index=*

What did I forget to do?

0 Karma
1 Solution

pil321
Communicator

Even though I was logged in as admin, the index that is searched by default for the admin user is only "main". Once I made the changes, everything worked.

View solution in original post

0 Karma

pil321
Communicator

Even though I was logged in as admin, the index that is searched by default for the admin user is only "main". Once I made the changes, everything worked.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

I consider it good practice to always write searches with the index(es) specified, then they work without relying on the indexes searched by default.

0 Karma
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...