| \n\nCheck\n\n \\[sn\\_sow\\_synthetics\\_check\\]\n\n | \n\nConfiguration information for synthetic checks.\n\n |
| \n\nCheck Execution Location\n\n \\[sn\\_sow\\_synthetics\\_check\\_execution\\_location\\]\n\n | \n\nExecution location configuration for synthetic checks.\n\n |
| \n\nSingle API\n\n \\[sn\\_sow\\_synthetics\\_check\\_single\\_api\\]\n\n | \n\nAdditional configuration information and last run results for single API synthetic checks.\n\n |
| \n\nSingle API Header\n\n \\[sn\\_sow\\_synthetics\\_check\\_single\\_api\\_header\\]\n\n | \n\nKey value pairs of requests headers for single API synthetic checks.\n\n |
| \n\nSingle API to Policy\n\n \\[sn\\_sow\\_synthetics\\_check\\_single\\_api\\_policy\\]\n\n | \n\nSingle API synthetic test data and its corresponding Agent Client Collector \\(ACC\\) policies.\n\n |
| \n\nSingle API Result\n\n \\[sn\\_sow\\_synthetics\\_check\\_single\\_api\\_result\\]\n\n | \n\nResults from each synthetic check run.\n\n |
| \n\nsn\\_sow\\_synthetics\\_recommendation\\_state\n\n | \n\nPer-endpoint creation state, idempotency\\_key, error tracking\n\n |
| \n\nsn\\_sow\\_synthetics\\_recommendation\\_telemetry\n\n | \n\nAggregate workflow metrics: card\\_shown, endpoints\\_discovered, monitors\\_created, workflow\\_status\n\n |
| \n\nSynthetic Private Locations\n\n \\[sn\\_sow\\_synthetics\\_private\\_location\\]\n\n | \n\nDefinitions of the ACC Agent Proxy Clusters available for synthetic monitoring. Extends the Proxy Agent Cluster \\[sn\\_agent\\_cluster\\] table.\n\n |
| \n\nsn\\_sow\\_synthetics\\_bulk\\_job\n\n | \n\nProvides async bulk job tracking.\n\n |
| \n\n`sn_sow_synthetics_location`\n\n | \n\nStores 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\n- Mid Server\n- ACC location\n\n |
| \n\n`sn_sow_synthetics_mid_location`\n\n | \n\nRepresents 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\\`.\n\n |
| \n\n`sn_sow_synthetics_mid_location_member`\n\n | \n\nStores the actual Mid Server assignments are saved in this table.\n\n |
| \n\n`sn_sow_synthetics_check_single_api_sysauto_script`\n\n | \n\nExtends 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.\n\n |
| \n\nsn\\_sow\\_synthetics\\_check\\_alert\n\n | \n\nA 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.\n\n |
| \n\nsn\\_sow\\_synthetics\\_check\\_single\\_api\\_policy\n\n | \n\nA 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.\n\n |
| \n\nsn\\_sow\\_synthetics\\_bulk\\_job\\_governance\n\n | \n\nDefines governance metadata for rate limiting and auditing for bulk jobs.\n\n |
\n