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!

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

New This Month - Observability Updates Give Extended Visibility and Improve User ...

This month is a collection of special news! From Magic Quadrant updates to AppDynamics integrations to ...

Intro to Splunk Synthetic Monitoring

In our last post, we mentioned that the 3 key pieces of observability – metrics, logs, and traces – provide ...