Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Domain separation and Operational Intelligence

Log in to subscribe to topics and get notified when content changes.

Domain separation and Operational Intelligence

This is an overview of domain separation and Operational Intelligence. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.

Overview

Support: Level 1

Domain separation is supported in this application. Not all ServiceNow applications support domain separation; some include limitations on the data and administrative settings that can be domain separated. To learn more, see Application support for domain separation.

How domain separation works in Operational Intelligence

When domains are separated in Operational 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 Operational Intelligence tables that are provided in the base system. The domain column shows the name of the domain to which the CI belongs.

Note: If the domain column does not appear in the list, click 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.
The following Operational Intelligence features have limited domain separation support.
Feature Support
Metric types

Supported at global level.

The instance owner can control the metric types for all domains.

Metric type registration

Supported at global level.

The instance owner can control the metric type registration for all domains.

Metric class

Supported at global level.

The instance owner can control the metric classes that are used for all domains.

Configuration settings rules

Supported at global level.

The instance owner can control the configuration settings rules for all domains

Configure domain separation

You can configure Operational Intelligence for domain separation to create logically defined domains that limit unauthorized access to data.

Before you begin

Role required: evt_mgmt_admin and evt_mgmt_integration

Procedure

  1. Activate the Domain Support – Domain Extension Installer plugin.
  2. Configure the MID Server for Operational Intelligence as a user that belongs to the desired domain with the role ‘mid_server’ assigned to it.
  3. Configure a MID Server distributed cluster in the domain you desire and add Operational Intelligence MID Servers that belong to the same domain. For more information about setting up MID Servers for Operational Intelligence, see MID Server and MID Server distributed cluster for Operational Intelligence.
Note: The Event Management’s binding events are configured using the domain of the logged-in MID Server user. Once the process has finished, the record’s domain is updated to use the domain from the CI so that any user within that domain can see the metric data.
Feedback