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

<table id=“table_hgx_ljr_qdc”><thead><tr><th>

Role

</th><th>

Description

</th><th>

Contains roles

</th></tr></thead><tbody><tr><td>

Synthetic monitor viewer

</td><td>

Views test configurations and their results.

</td><td>

• cmdb_read

• sn_sow.sow_user

• agent_client_collector_user

• sn_sow_synthetics.credential_reader

</td></tr><tr><td>

Synthetic monitor editor [sn_sow_synthetics.synthetics_editor]

</td><td>

Creates and edits tests. Views test configurations and their results.

</td><td>

• credential_admin

• sn_cmdb_editor

• sn_sow_synthetics.synthetics_viewer

</td></tr><tr><td>

Synthetic monitor admin [sn_sow_synthetics.synthetics_admin]

</td><td>

Assigns roles. Creates and edits tests. Views test configurations and their results.

</td><td>

• agent_client_collector_admin

• sn_sow_synthetics.synthetics_editor

• sn_sow_admin.sow_admin_center_user

</td></tr><tr><td>

Synthetic monitor credential reader

</td><td>

Used internally to read from the Credentials [discovery_credentials] table.

</td><td>

None

</td></tr><tr><td>

Synthetic monitor event writer

</td><td>

Used internally to communicate with the MID Server.

</td><td>

None

</td></tr></tbody> </table>## Tables installed

<table id=“table_fwf_y3r_qdc”><thead><tr><th>

Table

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Check

[sn_sow_synthetics_check]

</td><td>

Configuration information for synthetic checks.

</td></tr><tr><td>

Check Execution Location

[sn_sow_synthetics_check_execution_location]

</td><td>

Execution location configuration for synthetic checks.

</td></tr><tr><td>

Single API

[sn_sow_synthetics_check_single_api]

</td><td>

Additional configuration information and last run results for single API synthetic checks.

</td></tr><tr><td>

Single API Header

[sn_sow_synthetics_check_single_api_header]

</td><td>

Key value pairs of requests headers for single API synthetic checks.

</td></tr><tr><td>

Single API to Policy

[sn_sow_synthetics_check_single_api_policy]

</td><td>

Single API synthetic test data and its corresponding Agent Client Collector (ACC) policies.

</td></tr><tr><td>

Single API Result

[sn_sow_synthetics_check_single_api_result]

</td><td>

Results from each synthetic check run.

</td></tr><tr><td>

sn_sow_synthetics_recommendation_state

</td><td>

Per-endpoint creation state, idempotency_key, error tracking

</td></tr><tr><td>

sn_sow_synthetics_recommendation_telemetry

</td><td>

Aggregate workflow metrics: card_shown, endpoints_discovered, monitors_created, workflow_status

</td></tr><tr><td>

Synthetic Private Locations

[sn_sow_synthetics_private_location]

</td><td>

Definitions of the ACC Agent Proxy Clusters available for synthetic monitoring. Extends the Proxy Agent Cluster [sn_agent_cluster] table.

</td></tr><tr><td>

sn_sow_synthetics_bulk_job

</td><td>

Provides async bulk job tracking.

</td></tr><tr><td>

sn_sow_synthetics_location

</td><td>

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

</td></tr><tr><td>

sn_sow_synthetics_mid_location

</td><td>

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`.

</td></tr><tr><td>

sn_sow_synthetics_mid_location_member

</td><td>

Stores the actual Mid Server assignments are saved in this table.

</td></tr><tr><td>

sn_sow_synthetics_check_single_api_sysauto_script

</td><td>

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.

</td></tr><tr><td>

sn_sow_synthetics_check_alert

</td><td>

A 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.

</td></tr><tr><td>

sn_sow_synthetics_check_single_api_policy

</td><td>

A 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.

</td></tr><tr><td>

sn_sow_synthetics_bulk_job_governance

</td><td>

Defines governance metadata for rate limiting and auditing for bulk jobs.

</td></tr></tbody> </table>Parent Topic:Synthetic monitoring reference