Archive

How can we catch costly frozenTimePeriodInSecs typos?

Ultra Champion

Some of our production indexes were configured to have frozenTimePeriodInSecs = 777600 instead of frozenTimePeriodInSecs = 7776000, meaning, instead of 90 days they were configured to 9 days, which the client didn't like one bit when they found it.

What type of safeguards can we place to avoid such errors?

0 Karma
1 Solution

SplunkTrust
SplunkTrust

We have an alert that runs a few times in day to check if any index has data less than 90days and if so, we get an alert. We got bitten, when the admin deleted the buckets by mistake and had to put this alert to capture similar issues [ so, we can recover old data from backup etc..]

View solution in original post

0 Karma

SplunkTrust
SplunkTrust

We have an alert that runs a few times in day to check if any index has data less than 90days and if so, we get an alert. We got bitten, when the admin deleted the buckets by mistake and had to put this alert to capture similar issues [ so, we can recover old data from backup etc..]

View solution in original post

0 Karma

Ultra Champion

Absolutely @lakshman239 - that's the way to go !!!

0 Karma

SplunkTrust
SplunkTrust

I agree with the SE, seen it happen in the past.
double check your configurations, triple check indexes.conf

Ultra Champion

Sales Engineer is saying -

-- Configured is configured. No safeguards from a Splunk perspective.

Measure twice, cut once, have others review your changes.

0 Karma

Moderator
Moderator

Hi @ddrillic
Did the answer by @adonio help provide a working solution to your question? If yes, please don't forget to resolve this post by clicking "Accept". If no, please leave a comment with more feedback. Thanks!