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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

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

Get Updates on the Splunk Community!

What Is Splunk? Here’s What You Can Do with Splunk

Hey Splunk Community, we know you know Splunk. You likely leverage its unparalleled ability to ingest, index, ...

Level Up Your .conf25: Splunk Arcade Comes to Boston

With .conf25 right around the corner in Boston, there’s a lot to look forward to — inspiring keynotes, ...

Manual Instrumentation with Splunk Observability Cloud: How to Instrument Frontend ...

Although it might seem daunting, as we’ve seen in this series, manual instrumentation can be straightforward ...