Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feat] Switch From seq.json File to Splunk Checkpoint Feature #1

Open
3 tasks
8ear opened this issue Feb 19, 2019 · 1 comment
Open
3 tasks

[Feat] Switch From seq.json File to Splunk Checkpoint Feature #1

8ear opened this issue Feb 19, 2019 · 1 comment
Labels
enhancement New feature or request todo

Comments

@8ear
Copy link
Contributor

8ear commented Feb 19, 2019

Why

If you deploy your app with an deployment server, the deployment server replaces the whole app / ta folder to all heavy forwarder / search indexes / etc.. This replaces also the local folder in which the seq.json file is in place.

What

Remove the usage of external file for a sequence number and use the checkpoint function from the splunk python helper scripts.
https://docs.splunk.com/Documentation/AddonBuilder/2.2.0/UserGuide/PythonHelperFunctions

How

  • Remove seq.json requirement
  • Add checkpoint feature for sequence number
  • Test if it works
@8ear 8ear added enhancement New feature or request todo to discuss labels Feb 19, 2019
@8ear 8ear changed the title [Feat] switch from seq.json file to splunk checkpoint feature [Feat] Switch From seq.json File to Splunk Checkpoint feature Feb 19, 2019
@8ear 8ear changed the title [Feat] Switch From seq.json File to Splunk Checkpoint feature [Feat] Switch From seq.json File to Splunk Checkpoint Feature Feb 19, 2019
@8ear 8ear added todo and removed todo labels Apr 18, 2019
@geertjanvdk
Copy link
Contributor

This is not entirely correct. When an App is upgraded within Splunk, the /local folder is kept intact.
But yes, we should checkpoint to KV.

Note link:
https://docs.splunk.com/Documentation/AddonBuilder/3.0.2/UserGuide/PythonHelperFunctions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request todo
Projects
None yet
Development

No branches or pull requests

2 participants