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

Splunk Cloud Issues after 2.7.5 #32

Closed
zchef2k opened this issue Aug 8, 2019 · 0 comments
Closed

Splunk Cloud Issues after 2.7.5 #32

zchef2k opened this issue Aug 8, 2019 · 0 comments

Comments

@zchef2k
Copy link

zchef2k commented Aug 8, 2019

I submitted a request to reinstall the app after your 2.7.5 update and I was provided this by support:

This is a preliminary report. More issues may be found upon further review. Thank you for your app install request. Your app did not meet security and functionality requirements for Splunk Cloud for the following reasons: Blocking ConcernsFile: bin/web_ping.py, Line: 825This app contains a modular input [web_ping] which can start up to 5000 threads. This is not permitted in Splunk Cloud. The maximum number of threads we allowed is 25. Please set the validator of 'PARAM_THREAD_LIMIT' to IntegerFieldValidator(1, 25) in line 60 of bin/website_monitoring_rest_handler.py. And set the default thread_limit to no more than 25 in bin/web_ping.py.Non-Blocking ConcernsFile: README/website_monitoring.conf.spec, Line: 28There exists a proxy_password example which looks like a real password. It's better to use placeholders instead.Once these issues are remedied you can resubmit your app for review.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants