Skip to main content
A session is of type user, synthetics, or ci_test. A browser synthetic check that opens a page running the browser SDK makes a session of type synthetics; no setting is needed. Its events say the check, the run, and the location in synthetics.test_id, synthetics.result_id, and synthetics.location_id.

​
What it means for the numbers

The figures of an application are of real users, so a session a test drove is left out of:
  • the overview, performance, frustration, errors, analytics, heatmap, and feature flag pages, and the built-in dashboards;
  • alert rules on RUM figures;
  • the rows of the explorer and the RUM tools of Mole Agent.
Its errors do not open issues, so a failing check cannot count as a new issue. A page that left any out says N test sessions left out, which leads to them. Such a session is also not sampled: an application’s retention keeps it whole. When a filter of the application names session.type, the application has said what becomes of test runs, and they go by its filters and shares as any session does. The SDK keeps such a session whatever its own sessionSampleRate says.

​
Find them

  • From a run: Open the RUM session of this run, in the attempt of a result of a browser check.
  • From the session: the session page names the kind of session and leads to the results of the check.
  • In the explorer: a query that names session.type, synthetics.*, or ci_test.* is taken at its word, so session.type = 'synthetics' finds them. Without one, the explorer shows what real users did. The values of session.type are listed across every kind of session.
  • With the API, the same goes for the filters of search, aggregate, facets, and histogram.

​
Tests of an application

Set the same global before any script of the page runs. In Playwright:
The SDK sets window.__MOLESIGNAL_RUM_SESSION__ to the id of the session it recorded. A check reads it to link to the session, and leaves the page at the end of the journey so that the SDK sends what it holds.
A page has to run a browser SDK later than 0.2.0 for its session to say what drove it. The requests of the SDK go through the egress policy of the check like any other, so a policy that does not allow MoleSignal fails the check.
Last modified on October 31, 2026