Splunk Cloud Platform

Logs not ingested

abhi04
Communicator

Hi All,

I am unable to see the logs for the source even after seeing the file is being tailed and read in internal logs. Can you please guide as to what could be wrong here?

 

I can see in internal logs:
INFO Metrics - group=per_source_thruput, series="log_source_path",  kbps=0.056, eps=0.193, kb=1.730, ev=6, avg_age=0.000, max_age=0

 

But I dont see the logs in Splunk, the recent logs are there in file in the host, other sources are also coming into splunk fine.

 

 

 

Labels (1)
Tags (1)
0 Karma

abhi04
Communicator

@richgalloway well it goes to specific index, but I have also tried the below and I dont see the source or the events:

index=* host=abc | stats values(source) 

index=* source=log_source_path 
0 Karma

PickleRick
SplunkTrust
SplunkTrust

1. You can look for the source using metadata command

| metadata type=sources

or even

| metadata type=sources index=your_index

Alternatively you can use tstats

| tstats count where index IN (some, subset, of, your, indexes) source="your_source" by index

2. The data may not be findable due to a host of possible issues:

a) The data is indexed outside of your search timerange due to either data itself or wrong timestamp recognition

b) The configuration can be filtering/redirecting events to another index

c) The data may be being sent to a non-existent index and you don't have last-resort index defined

d) The source might be overwritten on ingestion.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

What search are you using to try to find the data?

---
If this reply helps you, Karma would be appreciated.
0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...