Cloud Support » History » Version 2
Version 1 (Luke Murphey, 06/02/2022 02:41 PM) → Version 2/4 (Luke Murphey, 06/02/2022 02:44 PM)
h1. Cloud Support
Website Monitoring will not allow users on Splunk Cloud to create inputs that are not using SSL (they are restricted to monitoring HTTPS). This is enforced in the backend code in the modular input (https://github.com/LukeMurphey/splunk-website-monitoring/blob/master/src/bin/web_ping.py) which will reject attempts to make an input that uses HTTP on Splunk Cloud and will refuse to run inputs on Cloud (in case the user crated an input manually via inputs.conf).
See the following line shows that the URL field is set to require HTTPS if on cloud:
<pre><code class="python">
URLField("url", "URL", "The URL to connect to (must be be either HTTP or HTTPS protocol)", empty_allowed=False, require_https_on_cloud=True),
</code></pre>
If someone wants to monitor an HTTP site, they need to run a forwarder outside of Splunk's Cloud environment.
Website Monitoring will not allow users on Splunk Cloud to create inputs that are not using SSL (they are restricted to monitoring HTTPS). This is enforced in the backend code in the modular input (https://github.com/LukeMurphey/splunk-website-monitoring/blob/master/src/bin/web_ping.py) which will reject attempts to make an input that uses HTTP on Splunk Cloud and will refuse to run inputs on Cloud (in case the user crated an input manually via inputs.conf).
See the following line shows that the URL field is set to require HTTPS if on cloud:
<pre><code class="python">
URLField("url", "URL", "The URL to connect to (must be be either HTTP or HTTPS protocol)", empty_allowed=False, require_https_on_cloud=True),
</code></pre>
If someone wants to monitor an HTTP site, they need to run a forwarder outside of Splunk's Cloud environment.