Monitor Configuration

The Monitor configuration file controls the probe identity, connectivity, scheduling behavior, browser automation settings, auto-thresholding, and vault integration.

Service Configuration (monitor.json)

This file must be in the same directory as the executable.

Full Example

{
  "name": "probe-paris-01",
  "port": "8051",
  "webserver": "192.168.1.100:8050",
  "integratorEndPoint": "192.168.1.100:8052",
  "location": "Paris, France",
  "description": "Production monitoring probe - Paris DC",
  "logLevel": "info",
  "concurrencyLimit": "100",
  "dataRetention": "336",
  "backupInterval": "24",
  "nbDaysBackup": "336",
  "maxBackups": "5",
  "maxSize": "10",
  "maxAge": "28",
  "logCompress": "true",
  "chromeBinPath": "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe",
  "firefoxBinPath": "",
  "edgeBinPath": "",
  "chromeVersion": "",
  "firefoxVersion": "",
  "edgeVersion": "",
  "autoThreshold": "true",
  "autoThresholdRange": "24",
  "autoThreshCri": "8",
  "autoThreshMaj": "6",
  "autoThreshMin": "4",
  "autoThreshTimeout": "10",
  "autoTransThreshold": "false",
  "vaultType": "",
  "hashiCorpVaultUrl": "",
  "hashiCorpVaultToken": "",
  "azureKVUrl": "",
  "cyberarkConjurUrl": ""
}

Settings Reference

Identity & Network

Data Management

Logging

Browser Configuration

Required for Web UI / EUM monitors that use Selenium WebDriver:

Auto-Thresholding

Automatically calculate performance thresholds based on historical data using standard deviation analysis:

How it works: A nightly job (02:00) collects the last N hours of performance data (autoThresholdRange), calculates the mean and standard deviation, then sets thresholds as:

Timeout  = mean + (autoThreshTimeout * stddev)   // hard execution cap
Critical = mean + (autoThreshCri     * stddev)
Major    = mean + (autoThreshMaj     * stddev)
Minor    = mean + (autoThreshMin     * stddev)

Notes:

• Only successful executions are included in the mean/stddev — failures and timeouts are excluded so a bad period does not poison the baseline.
• Only enabled monitors (state = on) are updated.
• autoTransThreshold runs the same computation per transaction step (02:05).
• Ping monitors additionally get jitter thresholds (jitterThreshCri/Maj/Min) computed from jitter mean + stddev with the same multipliers.

Percentile method (robust, recommended for noisy latency)

Set thresholdMethod to "percentile" to derive thresholds from the empirical latency distribution instead of mean+stddev. Latency is right-skewed, so percentiles match SLO semantics and resist outliers. The timeout is a high percentile times a safety factor, clamped to an absolute floor, which removes the near-zero-spread false-outage trap above.

The method applies to all monitor types — url, api, tcp, udp, ping, nslookup, db, snmp, wmi, sys and EUM transaction steps (exec). For EUM the per-step Minor/Major thresholds use autoThreshMinPct / autoThreshCriPct; steps below autoThreshMinSamples fall back to the legacy max×coefficient model.

Alert debounce (status-change flap suppression)

On-failure alerts are already debounced by the per-monitor notifyAfter / notifyFor settings (alert only after N consecutive breaches). debounceStatusChange extends the same consecutive-run guard to status-change notifications, so a single transient sample (e.g. a one-off timeout) no longer pages on the way out and back. Reuses the monitor’s existing notifyAfter as the depth.

Vault Integration

For retrieving secrets (passwords, API keys, TOTP seeds) from external vaults at runtime:

For how vault credentials and TOTP secrets reach EUM scenarios at runtime (VAULT_USERNAME_<urlTitle>, VAULT_PASSWORD_<urlTitle>, TOTP_SECRET_<urlTitle>), see the EUM Monitor page. For the end-to-end setup workflow, see Secret vaults.

Per-Monitor Settings

Each individual monitor has its own settings, configured via the Web UI or API. These are stored in the embedded key-value store, not in the JSON file.

Pattern Groups (URL & API)

URL and API monitors evaluate the response body with one or more pattern groups. Each group extracts a single value with its own regexp and grades it against its own thresholds. The monitor status is the most severe of every group status and the response-time status.

A single group can be configured through the legacy fields above (the primary group). Additional groups are stored in the patterns field as a JSON array; when it is set, it fully describes the evaluation (the primary group is its first entry).

Content match vs. value extraction

The primary pattern (pattern / patternUrl) works in two modes, chosen automatically by whether the regexp contains a capture group:

• Content match — no (capture group). A plain presence check: the response body must contain the pattern (substring or regexp). If it does not, the monitor fails (ERROR). No operator or thresholds apply; response-time thresholds still grade the timing.
• Value extraction — one (capture group). The captured text is graded against the operator and Minor/Major/Critical thresholds below. This is what a pattern group is.

Additional rows in the patterns array are always value-extraction groups. (A content-match primary combined with extra value groups is not re-checked in multi-group mode — keep the primary as a content match or a value group.)

Fields per group

Comparison operators

For every tier, the most severe matching tier wins; blank tiers are ignored, so a group can, for example, define only a Critical threshold.

patterns example

[
  { "name": "length",  "pattern": "\"length\"\\s*:\\s*(\\d+)", "matchIndex": "1",
    "comp": "number >", "min": "1000", "maj": "1500", "cri": "2000" },
  { "name": "fact",    "pattern": "\"fact\":(.*)",              "matchIndex": "1",
    "comp": "string contains", "min": "cats", "maj": "", "cri": "" },
  { "name": "updated", "pattern": "\"updated\":\"([^\"]*)\"",   "matchIndex": "1",
    "comp": "datetime older than", "min": "", "maj": "1h", "cri": "24h" }
]

Per-group captured values are stored under STATUS_PATTERN/<monitor>/<group> for history charts; groups removed or renamed are swept from the store on the next monitor save.

Translations

• fr: Configuration du Monitor