⚙️ 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:
|
Use case |
|---|
|
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:
|
Execution mode |
Description |
|---|---|
|
Manual |
A GermainUX user runs the action from Workspace and receives immediate success or failure feedback. |
|
Scheduled |
GermainUX runs the action automatically at a configured interval or time of day. |
|
Event-driven |
The action runs when a configured SLA, rule, insight, or automation condition occurs. |
An HTTP Action can be used to:
|
Action |
|---|
|
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:
|
Step |
|---|
|
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 scenarios are appropriate when browser rendering and visual interaction are not required.
For browser-level workflows involving clicks, forms, JavaScript, and page rendering, use a Click-Based Synthetic User Scenario.
⚖️ HTTP-Level vs. Click-Level Monitoring
|
Approach |
Best suited for |
|---|---|
|
HTTP/HTTPS Scenario |
APIs, services, endpoints, integrations, and protocol-level workflows. |
|
Click-Based Scenario |
Complete browser workflows, rendered pages, user interactions, and visual validation. |
See Configure an HTTP Action or Scenario.
Component: Engine
Feature Availability: 8.6.0 or later