HTTPS Checks operate exactly like our HTTP checks, but add in the relevant SSL/TLS concepts.
Control Panel Configuration
Select HTTPS from the monitoring catalog.
Similar to our HTTP checks, we have the same five checks available, just with a few more options.
HTTPS port configuration
HTTPS Port checks operate over port 443 and ensure that the port is available for connections.
HTTPS HEAD configuration
While the HTTPS Port check only tests if a port is reachable, the HTTPS HEAD check tests if a HEAD request will return its appropriate response. A HEAD request is used to ask only for information about the page and not the whole page itself. This can be useful if you do not want to use up your servers' bandwidth or use unnecessary resources. If the HTTPS HEAD check results in a 200 or a 300 status code, then the service is considered up, if it results in a 400 or a 500, then the service is considered down.
HTTPS check configuration
Our HTTPS checks have all the same options as HTTP but with the addition of SSL/TLS specific options. Within the SSL/TLS module, you can enable/disable certificate strictness and schedule warnings for expiration of SSL certificates. You can add the client-side certificate and the certificate private key within the Authentication module.
HTTPS browser synthetic check configuration
Get the tools
Before you can add an HTTP browser synthetic (multistep) check to your Panopta account, you need to download the Kantalon plugin for Chrome.
This plugin records and plays back user interactions with the browser. Use this to either create simple scripts or assist in exploratory testing.
We have a list of supported commands here.
Below is what the Katalon IDE plugin looks like, when opened:
Once you have the necessary plugins installed to record a browser synthetic check, open your browser, visit the site that is your test's starting point and start the plugin from the tools/extensions menu. Press the record button to start capturing your clicks and key presses.
The IDE will record all of your browsing actions until you tell it to stop by pressing the record button. The plugin is quite powerful and you can read more about it in Katalon Docs.
Once you're test session is complete, export the test as XML like so:
Select Browser Synthetic check from the metric list, then enter the source code under Check Source > Selenium Source.
Once entered, you can select Save and it will run every 10 minutes.
Testing branching, looping, or more advanced control flow
Checking the response content in detail
Testing API endpoints
Creating sessions or generating tokens via a separate API call
Testing against non-HTTP/s endpoints
HTTP page load - Test the speed of specific page load operations
FTP test - Connect to an FTP server or site, then check if an FTP file transfer is successful
Zip test - Download a zip file, then verify its contents
Configure the metric as usual.
If a check fails, an incident will be created depending on how you configure the metric's thresholds and alert timeline.