--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Domain separation and HLA # Domain separation and Health Log Analytics {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Domain separation and Health Log Analytics Domain separation in Health Log Analytics allows you to segregate data, processes, and administrative tasks into distinct logical groupings called domains. This ensures users access only the data relevant to their domain, enhancing data security and organizational clarity across multiple tenants or service providers. The application supports domain separation at runtime, encompassing user interface elements, cache keys, reporting, rollups, and aggregations. Show full answer Show less The feature is designed for Managed Service Providers (MSPs) and multi-tenant organizations that require strict isolation of log data and alerts within their respective domains. By default, all users and records belong to the parent domain, but admins can assign them to specific domains to enforce separation. ## Key Features * **Data and User Access Segmentation:** Users only see data and alerts within their assigned domain or child domains. * **Domain-Specific Alerts and Remediation:** Alerts generated by Health Log Analytics are domain-scoped, and remediation actions apply only within that domain. * **Transparent Domain Management:** The application handles domain separation seamlessly, managing system settings and custom operations per domain. * **Domain Separation Plugin:** Requires installation of the Health Log Analytics Domain Separation plugin (included from version 21.0.1) before configuring data inputs. * **Domain Assignment for Data Inputs:** Data inputs are configured to map log data into logical silos by domain, ensuring domain-specific processing and alerting. * **Centralized Server with Domain Isolation:** While system properties affecting the server are shared, most data and processing remain isolated per domain. * **Performance Considerations:** The server supports up to 60 KB events per second (EPS) across all domains without guaranteed SLAs per domain; heavy data streaming in one domain may impact others. ## Key Outcomes * **Improved Data Security and Privacy:** Sensitive logs and alerts are isolated within domains, protecting tenant-specific information. * **Efficient Multi-Tenant Management:** MSPs and organizations can manage multiple tenants in a single instance, simplifying administration and reducing overhead. * **Customizable Domain Access:** Admins can assign users and data inputs to specific domains, tailoring access and visibility appropriately. * **Domain-Scoped Alert Management:** Operators can view and respond to alerts only within their domain, preserving operational boundaries. * **Support for Multi-Tenant Use Cases:** Enables scenarios such as MSPs responding to tenant customer messages while maintaining domain data integrity. Domain separation is supported for Health Log Analytics. 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. ## Support level: Basic {#hla-domain-separation__section_isf_fwm_kqb} {#hla-domain-separation__domain-sep-supported} * Business logic: Ensure that data goes into the proper domain for the application's service provider use cases. * The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations. * The owner of the instance must set up the application to function across multiple tenants. {#hla-domain-separation__ul_yhr_g2j_xkb} Sample 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.{#hla-domain-separation__p_lsc_nfg_h1c} For more information on support levels, see [Application support for domain separation](https://www.servicenow.com/docs/access?context=domain-separated-apps&version=australia&pubname=australia-platform-security&ft:locale=en-US).{#hla-domain-separation__p_msc_nfg_h1c} ## Domain separation and Health Log Analytics overview {#hla-domain-separation__section_zmj_fwm_kqb} Domain separation is present in all aspects of the Health Log Analytics application. Users belonging to a specific domain see only the data existing in their own domain. ## How domain separation works in Health Log Analytics {#hla-domain-separation__section_anj_fwm_kqb} When data is domain separated using a single Health Log Analytics server, each Managed Service Provider (MSP) can see log data only in its own domain or child domains. Users can view alerts that Health Log Analytics generates only in their own domain. Actions to remediate the alerts apply only for the scope of that domain. By default, all users and records are set to the parent domain. The admin can assign them to a specific domain. The Health Log Analytics Domain Separation plugin must be installed before you configure your data inputs in the Health Log Analytics application. There is no setup procedure for the plugin. Install the plugin with the Health Log Analytics application Version 21.0.1 - September 2021, and then activate it. Make sure that you map your data into logical silos and configure rules and entities. You define the domain-separated environment when you configure your data inputs. Users can use data inputs that are only available in their own domain. Health Log Analytics creates alerts only for logs that arrive in those data inputs. All relevant records and all data processing in the Health Log Analytics program flow reside in the same domain as the data input. A data input's domain name is shown in the Domain column displayed in the tables in your instance. Using domain separation in your instance is transparent to Health Log Analytics. The application manages all aspects of the data, such as system settings and custom operations, separately. When a property is changed, the new value affects new sources only in the specific domain. System properties affecting the server are common to all domains because all domains use the Health Log Analytics server. Note: Health Log Analytics supports up to 60 kilobytes events per second (EPS) across all domains, without the ability to provide a service level agreement (SLA) to a specific domain and without fairness. If a domain streams a large amount of data, the Health Log Analytics server processes it. Other domains might suffer latency, drops, or other issues as a result, even if they stream a low number of logs. On the MID Server side, 10 kilobytes EPS is expected. ## Use cases {#hla-domain-separation__section_bnj_fwm_kqb} * An MSP wants to provide the Health Log Analytics application to multiple customers in a similar environment with a single instance. * An organization with many tenants wants to isolate its sensitive data, such as security logs. * An administrator of a tenant organization wants to define a data input only for their own domain. * An operator in a tenant organization wants to view logs only in their own domain. * An operator in a tenant organization wants to provide feedback for alerts only in their own domain. * An MSP Admin wants to view log data from all of their organization's tenant domains. {#hla-domain-separation__ul_qp1_wss_kqb} **Related topics** * [Domain separation for service providers](https://www.servicenow.com/docs/access?context=domain-sep-landing-page&version=australia&pubname=australia-platform-security&ft:locale=en-US)