Deploy to Mugnsoft

In this section you will learn how to turn a Pulse test into an EUM monitor that Mugnsoft runs on your probes, and how to commit it to GitLab.

Before you start

A Mugnsoft Core webserver, with at least one monitor probe that runs EUM monitors
The Mugnsoft connection set in Runtime settings, and verified with Test Connection
For GitLab, the GitLab connection set in Runtime settings
A test that passes reliably in Pulse

Open the monitor information

Hover over the test in the Tests tab and click Code exporter.
Keep Mugnsoft Code as language: the Generated Test Script window shows the script Mugnsoft will run.
Click Commit. The Monitor Information window opens, with three tabs.

The monitor information is saved with the test in the .side file, so the next deployment starts from the values you entered. See Monitor configuration in the .side file to keep the secrets out of it.

Settings

Card	Fields
Definition	Monitor Name and Description of the EUM monitor
Probes	The probes that run the monitor, read from your webserver
Schedule	The Frequency: 2, 3, 5, 10, 20 or 30 minutes, or 1 hour. The CUSTOM frequencies run only between a Start and an End time (09:00 to 17:00 by default)
Tags	Tags for linking — the tags that attach the monitor to your applications in Mugnsoft
Threshold	The Minor, Major and Critical limits and the Timeout of a run
Browser	The browser the probe uses: chrome, firefox or edge

A test whose first command is free text is a GUI test: the Browser card is replaced by GUI, with the image Similarity and the Capture .png zip of the images the test uses.

A red dot on the SETTINGS tab marks a required field left empty or invalid.

Advanced

Card	Fields
Misc	#Tries — the number of attempts of a run
Browser	Window size (2560x1440 to 1280x800), a specific User Agent, and a browser Extension (.crx) to load
Proxy	none, pac (with the Proxy PAC Url), basic (no auth), auth (with User and Password), or custom when the script sets it itself
Multi-Factor Authentication	Turn on TOTP and enter the Secret, for a journey that logs in with a one-time code
Key Vault	Read the credentials of the journey from a vault: Secret path, Username key and Password key
Connection quality	Throttling emulates a slower connection: Connection type (CELLULAR 2G, 3G or 4G, ETHERNET, WIFI), with its download, upload and latency

Actions

Choose who is alerted, and when, on each channel: Email (recipients), Slack (channel and token), Teams (webhook), PagerDuty (API key) and Custom script (the script to run and its Timeout (s)).

For each channel, ON FAIL alerts when the monitor fails and ON CHANGE when its status changes. The notify condition — notify if status is a given status, after a number of checks — filters out isolated failures, as for any Mugnsoft monitor.

Commit

The button at the bottom of the window deploys the monitor; its arrow offers three targets:

Commit to Mugnsoft — creates the EUM monitor on the webserver of the selected environment. It then appears in the monitors listing of Mugnsoft.
Commit to Gitlab — commits the monitor definition to your repository, with the GITLAB COMMIT MSG you enter. Choose the ACTION: Create a new definition, Update an existing one, or Delete it.
Commit to Mugnsoft and Gitlab — both at once.

Note:

Deploying sends the script, the monitor settings and its secrets to the webserver. Use an HTTPS connection to the webserver, and a token with a limited validity.