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)
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

ATTENTION: We’re Moving! (AGAIN!)

The Splunk Community Slack is undergoing a system migration to keep our workspace secure and ...

Deep Dive: Optimizing Telemetry Pipelines in Splunk Observability Cloud

In this session, we will peel back the layers of Splunk Observability Cloud’s cost-optimization features. ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...