Getting Data In

Logs not flowing to splunk index from GCP -Solution

splunkeremy
Engager

Hi Everyone!.

I'm here to share the resolution for one of the frequent errors that we see in internal logs and sourcetype=splunkd.

If you happen to encounter the below error,

"Failed processing http input , token name=token_name,parsing_err="Incorrect index", index=index_name"

Please make sure that your index name is being added to the respective token(HEC).

In order to avoid this error, make sure your index is added under the respective token as soon as a new index is created.

[https://token name]

disabled = 0

index=default_index name

indexes=index1,index2, index3;[add your index here]

 

Cheers

 

 

 

Labels (1)
Get Updates on the Splunk Community!

Index This | What is broken 80% of the time by February?

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

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...