Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Components installed with synthetic monitoring

Several types of components are installed with activation of the synthetic monitoring plugin, including tables and user roles.

Roles installed

RoleDescriptionContains roles
Synthetic monitor viewer\[sn\_sow\_synthetics.synthetics\_viewer\]Views test configurations and their results.- cmdb\_read - sn\_sow.sow\_user - agent\_client\_collector\_user - sn\_sow\_synthetics.credential\_reader
Synthetic monitor editor \[sn\_sow\_synthetics.synthetics\_editor\]Creates and edits tests. Views test configurations and their results.- credential\_admin - sn\_cmdb\_editor - sn\_sow\_synthetics.synthetics\_viewer
Synthetic monitor admin \[sn\_sow\_synthetics.synthetics\_admin\]Assigns roles. Creates and edits tests. Views test configurations and their results.- agent\_client\_collector\_admin - sn\_sow\_synthetics.synthetics\_editor - sn\_sow\_admin.sow\_admin\_center\_user
Synthetic monitor credential reader\[sn\_sow\_synthetics.credential\_reader\]Used internally to read from the Credentials \[discovery\_credentials\] table.None
Synthetic monitor event writer\[sn\_sow\_synthetics.synthetics\_event\_writer\]Used internally to communicate with the MID Server.None

Tables installed

TableDescription
Check \[sn\_sow\_synthetics\_check\]Configuration information for synthetic checks.
Check Execution Location \[sn\_\_sow\_synthetics\_check\_execution\_location\]Execution location configuration for synthetic checks.
Single API \[sn\_sow\_synthetics\_check\_single\_api\]Additional configuration information and last run results for single API synthetic checks.
Single API Header \[sn\_sow\_synthetics\_check\_single\_api\_header\]Key value pairs of requests headers for single API synthetic checks.
Single API to Policy \[sn\_sow\_synthetics\_check\_single\_api\_policy\]Single API synthetic test data and its corresponding Agent Client Collector \(ACC\) policies.
Single API Result \[sn\_sow\_synthetics\_check\_single\_api\_result\]Results from each synthetic check run.
sn\_sow\_synthetics\_recommendation\_statePer-endpoint creation state, idempotency\_key, error tracking
sn\_sow\_synthetics\_recommendation\_telemetryAggregate workflow metrics: card\_shown, endpoints\_discovered, monitors\_created, workflow\_status
Synthetic Private Locations \[sn\_sow\_synthetics\_private\_location\]Definitions of the ACC Agent Proxy Clusters available for synthetic monitoring. Extends the Proxy Agent Cluster \[sn\_agent\_cluster\] table.
sn\_sow\_synthetics\_bulk\_jobProvides async bulk job tracking.
`sn_sow_synthetics_location`Stores the top-level execution locations used to run synthetic monitors. Each location represents a network vantage point and can be one of the following:- Hosted - Mid Server - ACC location
`sn_sow_synthetics_mid_location`Represents a logical grouping of one or more MID Servers that act as a named execution location for synthetic monitors. This record provides the name and description for a Mid Server-based location. The actual MID Server assignments are stored in \`sn\_sow\_synthetics\_mid\_location\_member\`.
`sn_sow_synthetics_mid_location_member`Stores the actual Mid Server assignments are saved in this table.
`sn_sow_synthetics_check_single_api_sysauto_script`Extends the platform \`sysauto\_script\` \(Scheduled Script Execution\) table to associate a scheduled background job with a specific Single API check. Each record represents the scheduled job responsible for periodically triggering a synthetic monitor run for its linked check. Records are automatically created, updated, and deleted by the application when a check's location or configuration changes.
sn\_sow\_synthetics\_check\_alertA join table that links a synthetic check to an Event Management alert. When a synthetic monitor detects a failure, the platform creates a record here to track the relationship between the failing check and the alert it generated. Records are cascade-deleted when either the check or the alert is removed.
sn\_sow\_synthetics\_check\_single\_api\_policyA joint table that maps a Single API check to its associated ACC agent policy. This relationship is used when a check runs via an ACC Proxy Cluster location and the policy governs what the ACC agent is authorized to execute. Records are cascade-deleted when the linked check is removed, and the application automatically manages this table when ACC-based checks are created or updated.
sn\_sow\_synthetics\_bulk\_job\_governanceDefines governance metadata for rate limiting and auditing for bulk jobs.

Parent Topic:Synthetic monitoring reference