How to set up Performance Analytics on a domain-separated instanceIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Learn how to configure Performance Analytics (PA) on a domain-separated instance, including how domain context affects score collection, how to use the Domain Support plugin, and how to handle data tables versus process tables. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All supported releases Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } How domain separation affects PA score collection The PA Scores tables — [pa_scores], [pa_scores_l1], and [pa_scores_l2] — are domain-separated tables. Each score collected on a domain-separated instance has a domain associated with it. The domain assigned to a score is determined by one of the following: The domain of the run as user configured on the Data Collection JobA domain configuration record (when the Domain Support plugin is active) Using the Domain Support plugin The Domain Support plugin (com.snc.pa.domain_support) provides access to the Domain Configuration feature, which enables score collection across multiple domains using a single Data Collection Job. When a domain configuration record is used, the plugin adds additional query parameters to Indicator and Breakdown Sources so that records from multiple domains are returned. The results are then aggregated per domain, and a separate score is recorded for each domain. Data tables versus process tables Regardless of whether a domain configuration is used, the domain context of a Data Collection Job is always determined by the run as user. Data tables For data tables — for example, [incident] — using a global domain administrator as the run as user is common practice. Due to domain rules on data tables, this user has full visibility of all records across domains. This approach works correctly in most cases. Process tables Process tables are tables that include a sys_overrides field — for example, [contract_sla]. When a run as user from the global domain collects scores on a process table, visibility is restricted to global domain records only. Records defined on child domains are not visible to the data collector. This restriction also applies to database views that join to a process table — for example, [incident_sla] joins to [contract_sla] and inherits the same visibility restriction. MSP considerations Managed service providers (MSPs) commonly define process records — such as business rules, SLAs, and client scripts — on process domains rather than in the global domain. When this is the case, Data Collection Jobs that use process table sources require a run as user with appropriate visibility into those process domains. For a detailed overview and step-by-step guidance for setting up Performance Analytics on a domain-separated instance in an MSP environment, see the attached best practice document.