Skip to main content
Free plan, no cardStart free

MONSynthetic monitoring · updated 2026-11-10

Synthetic monitoring tool: scheduled checks with alerts

A recorded flow or an API check on a timetable, uptime and response time, alerts to Slack, Teams, Opsgenie or a webhook once a rule holds across consecutive checks.

For: Teams that want to know a sign-in, a checkout or an API has broken before the first support ticket, and on-call engineers who want alerts in the channel they already watch, with no second agent to install.

acme-shop / checkout-flow.recIllustrative run
  1. REGRegressionPassed14 / 14 steps · 38.2 s
  2. LOADLoad · 200 virtual usersIn budgetP50 180 · P95 412 · P99 690 ms
  3. SECSecurity · OWASP Top 10 (2025)1 confirmed1 confirmed · 2 observed
  4. A11YAccessibility · WCAG 2.2 A and AA3 issues9 pages · VPAT draft ready
1 selector healed#pay-now-btn[data-test="pay"]Shown in the run

Capabilities

A recorded flow as a monitor

Pick a recording, choose the interval, and the flow replays in a real pooled browser on that timetable. A step the replayer cannot run is reported as skipped, never counted as passed, and a bot-challenge page halts the check as blocked rather than passing its buttons.

Read more: A recorded flow as a monitor

API checks with assertions

A method, a URL, headers and a body, with assertions on the status code or range, latency, a header, body text, a JSON path or a regular expression, run on an interval you set and on demand with Run now.

Read more: API checks with assertions

Uptime and response time

Per monitor: uptime, total checks, the response-time trend and an uptime strip; across monitors, the overall uptime on the dashboard.

Alert rules with hysteresis

Four conditions (consecutive failures, uptime below a percentage, response time above a limit, error rate above a limit) with a threshold and a cooldown each. A rule opens only after its condition has held for consecutive checks and resolves the same way, so one slow check does not page anyone.

Alert sinks you own

A Slack incoming webhook, a Microsoft Teams webhook, the Opsgenie alert API or a generic webhook, each with a minimum severity and a test button. Alerts post to every sink at or above its severity.

Read more: Alert sinks you own

Honest about where it ran

Every check records three things separately: the location you asked for, the lane that actually carried it (none means the Dokimore server in India) and the country observed from that lane, so a result never claims a location it did not use.

How it works

  1. Record the flow, or name the endpointA journey the recorder captured, or an API request with its assertions.
  2. Create the monitorA name, the recording or the request, and the interval: every 1, 5, 15, 30 or 60 minutes.
  3. Add the sinksSlack, Microsoft Teams, Opsgenie or a webhook, each with a minimum severity; press the test button once.
  4. Read the dashboard, act on alertsUptime, the response-time trend and each check’s step results; an alert names the rule and the checks that opened it.

What you receive, and what we do not do

Evidence ledger
Per check
Pass, fail, skipped or error; the result and duration of each step; the response time; the location requested, the lane used and the country observed.
Per alert
The rule, its threshold, the consecutive checks that opened it, the sinks it reached and when it resolved.
Per monitor
Uptime, total checks and the response-time trend over time.

Limits we state

  • Checks run from Dokimore’s servers in India. A location chosen on the form is recorded as the request; the check records separately which lane carried it, which is none unless Dokimore has set one up for your tenant.
  • Only synthetic-monitor alerts leave the platform: failed test runs and other events are not posted to the sinks, and a message carries no link to a run.
  • PagerDuty is not connected: route alerts through Opsgenie or a webhook relay. No e-mail and no Jira ticket is sent from an alert yet.
  • A browser check that finds no free browser slot is recorded as skipped for lack of capacity, never as a pass and never as a failure of your site.

Plans: On every plan, including Free: monitors live under Developer Experience, which every plan opens with recordings, and alert sinks are on every plan. There is no published cap on monitors; browser checks share the platform’s browser capacity. See the metering table.

Questions buyers ask

What is synthetic monitoring?

Running a scripted check against your application on a timetable, from outside it, and alerting when the check fails or slows: the opposite of waiting for a real user to report the problem. The check here is either a recorded browser flow replayed in a real browser or an API request with assertions.

Does a monitor run from several regions?

No. Checks run from Dokimore’s servers in India. The location labels on the form are recorded as what you asked for, and each check records separately which lane actually carried it, so the result is honest about where it ran.

Which alert channels are supported?

Slack through an incoming webhook, Microsoft Teams through a webhook, Opsgenie through its alert API, and any HTTPS endpoint through a generic webhook sink. PagerDuty is not connected; an Opsgenie sink or a webhook relay reaches it. Each sink has a minimum severity.

Can an API collection run as a monitor?

Yes, two ways. In the API studio a collection runs on a schedule as a monitor with its assertions and timing. Under Developer Experience a single API check with its own assertions runs on an interval you set, beside the browser monitors built from recordings.

Why did a check come back as skipped?

Browser checks share the platform’s browser capacity. When no slot is free at the moment of the check, the result is recorded as skipped for lack of capacity, which is deliberately neither a pass nor a failure of your site.

Try it on your own application

The Free plan asks for no card and runs for 14 days after the trial. Or bring one flow from your product and we record it live.

  • Free plan, no card
  • 14-day Solo Pro trial
  • Demo replies within one business day
  • Data hosted in India