Monitoring Splunk

how to make my splunk work fast ??

Path Finder

Hi ,

Actually my splunk has 6 yrs of data , i think this is the reason for the slowness .
Now i need to make this fast.I can reduce the data from 6 yrs to latest 1 yr .

I need to archive the remaining 5 yrs data , for the future use and not deleting it permanently.
Need help to do this process in splunk.Please provide all the settings that are need to be changed,since i am new to this archiving stuff.

Regards,
Sundar

0 Karma
1 Solution

Legend

Hi umsundar2015,
the problem having 6 years on line is present only if you use "Always" as search Time period, if you use e.g. "last month" you will not have differences between 1 year and 6 years archived.
The real problem usually is the throughput of your storage, what is IOPS value of it?
you can test it using many tools as open source Bonnie++, remember that Splunk requires at least 800 IOPS (better 1200).
In addition, what kind of searches you run: full text searches or field searches? do you always use index=.. in your searches?
this is another point of attention, there are some best practice to optimize searches (http://docs.splunk.com/Documentation/SplunkCloud/6.6.0/Search/Quicktipsforoptimization ).

Bye.
Giuseppe

View solution in original post

0 Karma

Esteemed Legend

As @cusello said, long retention is only a problem for speed if you are searching all of it. Are you? If you are, look into a Summary Index or Accelerated Data Model. If not, then you have some other problem.

0 Karma

Legend

Hi umsundar2015,
the problem having 6 years on line is present only if you use "Always" as search Time period, if you use e.g. "last month" you will not have differences between 1 year and 6 years archived.
The real problem usually is the throughput of your storage, what is IOPS value of it?
you can test it using many tools as open source Bonnie++, remember that Splunk requires at least 800 IOPS (better 1200).
In addition, what kind of searches you run: full text searches or field searches? do you always use index=.. in your searches?
this is another point of attention, there are some best practice to optimize searches (http://docs.splunk.com/Documentation/SplunkCloud/6.6.0/Search/Quicktipsforoptimization ).

Bye.
Giuseppe

View solution in original post

0 Karma

SplunkTrust
SplunkTrust

You can move old data to Frozen bucket. You also need to check your data rolling policy (based on size or age) for various bucket. Hot and Warm buckets return data faster and contain current/recent data.
For specific settings based on your infrastructure you should go through the following documentation very carefully: http://docs.splunk.com/Documentation/Splunk/latest/Indexer/HowSplunkstoresindexes And http://docs.splunk.com/Documentation/Splunk/latest/Indexer/Automatearchiving

You can also see feasibility of Summarizing older data if possible and required using collect command.

____________________________________________
| makeresults | eval message= "Happy Splunking!!!"
0 Karma