Monitoring Splunk

With coldToFrozenScript, what is responsible for deleting the bucket?

dwaddle
SplunkTrust
SplunkTrust

When you specify a coldToFrozenScript in indexes.conf, what is responsible for deleting the cold bucket from the indexer's disc? (eg, is it your script, or does Splunk delete it once your script has done whatever it's gonna do?)

I would have assumed the script would be responsible, but the example of compressedExport.sh does not show it actually deleting the bucket's data from the disk.

Tags (1)
1 Solution

amrit
Splunk Employee
Splunk Employee

Splunkd will delete the bucket after running your coldToFrozenScript. Your script can delete the bucket if it wishes, and Splunkd will handle this case without errors, but the main reason for the script is to give you a chance to archive your data however you wish before the bucket is deleted.

View solution in original post

amrit
Splunk Employee
Splunk Employee

Splunkd will delete the bucket after running your coldToFrozenScript. Your script can delete the bucket if it wishes, and Splunkd will handle this case without errors, but the main reason for the script is to give you a chance to archive your data however you wish before the bucket is deleted.

Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

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 ...