Deployment Architecture

Why is the earliest event in an index not reflective of what is displayed on the Cluster Master?

ankithreddy777
Contributor

On the Distributed Management Console tab on Cluster Master (CM), I found that earliest event in one of my console is May 10 2015 .
But when I search data in that index (Clustered) it only returns the data from Dec 15 2015. Also also used metadata command for that index, which is also showing the first time = Dec 15 2015.

May I know why the console on CM is showing earliest event is at MAY 10, 2015?

0 Karma

muebel
SplunkTrust
SplunkTrust

Hi ankithreddy777, it might be possible that the management console is looking over all indexes to find the earliest event. You can be certain of the starting point in time for you indexes by running this command over all time:

| tstats min(_time) as earliest_time, max(_time) as latest_time by index | convert ctime(*time)

This will give you the earliest as well as most recent event time for each index the search head is able to access.

Please let me know if this helps!

0 Karma

muebel
SplunkTrust
SplunkTrust

whats the path to the dashboard that is show the May 10 2015 reading?

0 Karma
Get Updates on the Splunk Community!

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...

Updated Team Landing Page in Splunk Observability

We’re making some changes to the team landing page in Splunk Observability, based on your feedback. The ...