{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":31221,"path":"it-operations-management/metric-intelligence/domain-separation-operational-intelligence.md","title":"Domain separation and Metric Intelligence","bundle":null,"doc_type":null,"release":"australia","body":"\n# Domain separation and Metric Intelligence\n\nDomain separation is supported in Metric Intelligence. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.\n\n## Support level: Basic\n\n\n\n-   Business logic: Ensure that data goes into the proper domain for the application’s service provider use cases.\n-   The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations.\n-   The owner of the instance must set up the application to function across multiple tenants.\n\nSample use case: When a service provider \\(SP\\) uses chat to respond to a tenant-customer’s message, the customer must be able to see the SP's response.\n\nFor more information on support levels, see [Application support for domain separation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/domain-separated-apps.md).\n\n## How domain separation works in Metric Intelligence\n\nWhen domains are separated in Metric Intelligence, users can view and manage alerts and events only in their own \\(tenant\\) domain. After the binding process has finished, the domain of the configuration item \\(CI\\) is used so that users within that domain can explore metric data. A domain column is present for Metric Intelligence tables that are provided in the base system. The domain column shows the name of the domain to which the CI belongs.\n\n**Note:** If the domain column does not appear in the list, click \\[Omitted image \"PersonalizeIcon.png\"\\] Alt text: Personalize List to add a column\\(Personalize List\\) and add the required column. In addition, you can add a column that displays the domain path.\n\nThe following Metric Intelligence features have limited domain separation support.\n\n<table id=\"table_b3x_svh_l2b\"><thead><tr><th>\n\nFeature\n\n</th><th>\n\nSupport\n\n</th></tr></thead><tbody><tr><td>\n\nMetric types\n\n</td><td>\n\nSupported at global level.\n\n The instance owner can control the metric types for all domains.\n\n</td></tr><tr><td>\n\nMetric type registration\n\n</td><td>\n\nSupported at global level.\n\n The instance owner can control the metric type registration for all domains.\n\n</td></tr><tr><td>\n\nMetric class\n\n</td><td>\n\nSupported at global level.\n\n The instance owner can control the metric classes that are used for all domains.\n\n</td></tr><tr><td>\n\nConfiguration settings rules\n\n</td><td>\n\nSupported at global level.\n\n The instance owner can control the configuration settings rules for all domains\n\n</td></tr></tbody>\n</table>**Related topics**  \n\n\n[Domain separation for service providers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/domain-sep-landing-page.md)\n\n"}}