Troubleshooting
jzsplunk edited this page Aug 18, 2020
·
5 revisions
-
CI validates that the content was written to spec using
validate.py. To run validation manually, run:python bin/validate.py --path . --verbose. -
CI generates Splunk configuration files using
generate.py. If you want to export Splunk .conf files manually from the content, runpython bin/generate.py --path . --output package --verbose. - CI builds a DA-ESS-ContentUpdate Splunk package using the Splunk Packaging Toolkit.
- CI tests the newly produced package using Splunk Appinspect.
- note that requirements.txt hard codes the versions for packages we use dependabot to make sure we safely always upgrade to the latest versions.
- Detection schema and jinja template related troubleshooting can be tested with:
python bin/generate.py -p . -o package
Please use the GitHub Issue Tracker to submit bugs or request features.
If you have questions or need support, you can:
- Post a question to Splunk Answers
- Join the #security-research room in the Splunk Slack channel
- If you are a Splunk Enterprise customer with a valid support entitlement contract and have a Splunk-related question, you can also open a support case on the https://www.splunk.com/ support portal