Knowledge Management

SmartStore, why ES requires 90days local

damindragunatil
Explorer

Hi, can someone answer the reason for Splunk SmartStore requiring 90days of local storage when using Enterprise Security rather than 30days?

Many thanks in advance

 

Labels (1)
0 Karma
1 Solution

scelikok
SplunkTrust
SplunkTrust

Hi @damindragunatil,

ES needs to span 90 days historical data for baselining. This is mostly used for detecting historical anomalies. 

Another reason is datamodel accelerations/backfills. These process scans old data to check if there is any data that has not accelerated yet.

Periodically accessing old events may result huge eviction and download processes which will affect your overall performance. That is why 90 days cache is recommended.

If this reply helps you an upvote and "Accept as Solution" is appreciated.

View solution in original post

damindragunatil
Explorer

Thank you for the explanation, very much appreciated.

Regards

Damindra

0 Karma

scelikok
SplunkTrust
SplunkTrust

Hi @damindragunatil,

ES needs to span 90 days historical data for baselining. This is mostly used for detecting historical anomalies. 

Another reason is datamodel accelerations/backfills. These process scans old data to check if there is any data that has not accelerated yet.

Periodically accessing old events may result huge eviction and download processes which will affect your overall performance. That is why 90 days cache is recommended.

If this reply helps you an upvote and "Accept as Solution" is appreciated.
Get Updates on the Splunk Community!

New Case Study Shows the Value of Partnering with Splunk Academic Alliance

The University of Nevada, Las Vegas (UNLV) is another premier research institution helping to shape the next ...

How to Monitor Google Kubernetes Engine (GKE)

We’ve looked at how to integrate Kubernetes environments with Splunk Observability Cloud, but what about ...

Index This | How can you make 45 using only 4?

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