HTTP/HTTPS Action Execution
Execution behavior for actions
HTTP/HTTPS Scenario Execution
How scenarios run over HTTP
HTTP-Level vs. Click-Level Monitoring
Choosing request or browser depth
GermainUX HTTP/HTTPS Requests
GermainUX can execute HTTP or HTTPS requests manually, on a schedule, or in response to an automated condition. These requests can support:- Availability and uptime checks
- API and endpoint validation
- HTTP-level synthetic scenarios
- Transaction triggering
- Integration testing
- Automated remediation
- Port and service checks
- Custom operational workflows
HTTP/HTTPS Action Execution
An HTTP/HTTPS Action sends a request to a configured endpoint or data source. It can be executed:
An HTTP Action can be used to:
- Confirm that an endpoint is available.
- Trigger a remote transaction or job.
- Call an application or infrastructure API.
- Validate an expected response.
- Initiate a recovery or remediation workflow.
- Test connectivity from a specific GermainUX Engine.
HTTP/HTTPS Scenario Execution
An HTTP Scenario executes a sequence of HTTP or HTTPS requests representing a user or business workflow at the protocol level. For example, a scenario can:- Authenticate with an application or service.
- Submit one or more API requests.
- Validate response status or content.
- Pass data between requests.
- Measure the duration of the complete transaction.
- Report success, failure, and performance to GermainUX.
HTTP-Level vs. Click-Level Monitoring
See Configure an HTTP Action or Scenario.
Get Help
Contact GermainUX Support
The Germain Team can help you set this up.
Can't find what you need?
Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.
The content of this document is proprietary to GERMAIN SOFTWARE LLC.