All Apps and Add-ons

Where does the Splunk Add-on for Box store checkpoint information?

scsvnovonordisk
New Member

I recently install the add-on and it appears to be working fine. However, I'd like to understand more around how the app works. Can someone explain how the add-on stores checkpoint information and where it puts it on the file system?

I found the created_after variable in the box_default section of box.conf, but it doesn't appear to have been changed since I installed the add-on. The python is a bit complicated but I see reference to a checkpoint_dir setting (which I don't see set anywhere, nor can I tell what it defaults to) as well as it functions that look like they use the rest_api to save the checkpoint somewhere. But i don't see what rest endpoint it uses.

Can somebody help me figure it out?
Thanks!

Tags (1)
0 Karma
1 Solution

rpille_splunk
Splunk Employee
Splunk Employee

Have you checked the documentation? http://docs.splunk.com/Documentation/AddOns/released/Box/Troubleshooting#Reset_checkpoint_for_histor... suggests that there is an events checkpoint file under $SPLUNK_HOME/var/lib/splunk/modinputs/box_service.

View solution in original post

rpille_splunk
Splunk Employee
Splunk Employee

Have you checked the documentation? http://docs.splunk.com/Documentation/AddOns/released/Box/Troubleshooting#Reset_checkpoint_for_histor... suggests that there is an events checkpoint file under $SPLUNK_HOME/var/lib/splunk/modinputs/box_service.

scsvnovonordisk
New Member

Totally missed that page. Thanks!

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...