EUM Monitor (Web UI)

The EUM (End User Monitoring) monitor type executes multi-step user journeys in a real web browser, exactly as an end user would experience them. This page is the full specification of the EUM engine: capabilities, scenario script functions, TOTP/MFA support, and secrets/key-vault integration.

Overview

EUM scenarios are executed headless by default on the probe; each run replays the recorded journey, measures every declared transaction, and reports timings, screenshots, video, and HAR data back to the Webserver.

Capabilities

• Multi-step transaction recording (via MNS IDE or Selenium IDE)
• Individual transaction timing with critical/major thresholds, enriched with window.performance browser metrics
• Screenshot capture: on error, per transaction, or on every step (photo mode)
• Video recording of the entire execution
• HAR (HTTP Archive) capture of all network traffic through the embedded proxy
• TOTP (Time-based One-Time Password) support for 2FA / MFA
• Encrypted credentials — embedded (AES) or retrieved from an external key vault at runtime
• Corporate proxy configuration
• Visual similarity checking

Scenario Script Functions

Scenario files are generated by the MNS IDE recorder and call the following built-in functions:

Example:

mnsStartTransaction("Login Page", 30, 5000, 3000); // name, timeout, critical_ms, major_ms
driver.findElement(By.id("username")).sendKeys("user");
driver
  .findElement(By.id("password"))
  .sendKeys(MNSDecrypt("q1hjZXR0ZSBjbGUgZXN0..."));
driver.findElement(By.id("submit")).click();
mnsStopTransaction();

Encrypted password

wherever required, use any of the jar file in the monitor exec folder: MNSCliXXX.jar

cd <monit_home>\exec\jdk\bin\java.exe -jar -DpwdEncrypt=78814630Mdp!! MNSCliOnDemand.jar
skYMPogdjkDvTwy6RwVPMw==

Then in the scenarion or Mugnsoft Pulse, use that previously generated string in the MNSDecrypt private function. For instance MNSDecrypt(“skYMPogdjkDvTwy6RwVPMw==") with the above example.

driver
  .findElement(By.name("password"))
  .sendKeys(MNSDecrypt("skYMPogdjkDvTwy6RwVPMw==")); //wil be decrypted as "78814630Mdp!!");

TOTP / MFA Support

The EUM engine can generate TOTP codes during a scenario, allowing monitors to log in to applications protected by two-factor authentication. Wherever the totp code number is required, replace with a protected keyword totpCode.

In advanced tab of the monitor information:

• check the totp
• add the secret

Then you can deploy it and the totpCode will be computed accordingly during the scheduled replay.

Supported specification: RFC 6238

These are the same parameters used by Google Authenticator, so any identity provider offering a “Google Authenticator”-style TOTP enrollment is compatible — including Okta, Microsoft Entra ID, Google, and Duo.

The TOTP shared secret is stored AES-encrypted and delivered to the engine at runtime through the TOTP_SECRET_<urlTitle> environment variable.

Okta compatibility

Secrets & Key-Vault Integration

EUM scenarios never store passwords in clear text. Two mechanisms are available:

1. Embedded encrypted credentials

Passwords can be embedded directly in the scenario as AES-encrypted strings and decrypted at runtime with MNSDecrypt("..."). Operators generate the encrypted strings with the engine’s password-encrypt mode and paste them into the scenario.

2. External key vaults

Credentials can be retrieved at runtime from an external secrets manager, so they never appear in the scenario at all. When credentials stored in a Vault are required, replace them with the protected keywords vaultUsername and vaultPassword.

vaultUsername
vaultPassword

In the monitor configuration, associate the Vault containing the credentials to be used.

Once the monitor is deployed, the vaultUsername and vaultPassword values will be automatically replaced with the credentials retrieved from the Vault during scenario execution. This ensures that authentication information is never stored in plain text within the script or scenario.

At execution time, the retrieved credentials are delivered to the scenario through per-monitor environment variables:

Vault connection settings (vaultType, URLs, tokens) are configured on the Monitor probe — see Monitor Configuration → Vault Integration.

Translations

• fr: Moniteur EUM (Web UI)