Best practices guidelines on Domain separation and CSDM

[Servicenow lear]

>>Which  CSDM domain helps in identifying responsible parties in issues due to DevOps application changes. Any documentation or reference on this.

>>What are the issues identified when we activate domain seperation on an active Instance ? Any product documentation or guidelines associated with it ?  Any reference would be great.

[Yousaf]

Hi,
1.  Configuration Management (CMDB) domain is responsible for identifying and tracking the configuration items (CIs) that make up the infrastructure of an IT environment. In the context of DevOps and application changes, the CMDB can be used to identify the responsible parties for issues that arise as a result of these changes.

The CMDB can store information about the relationships between CIs, including the ownership and responsibility for each CI. This information can be used to quickly identify the parties responsible for specific components of an IT infrastructure and help with resolving issues that arise from application changes.

By keeping a comprehensive and up-to-date record of the IT infrastructure and its components, the CMDB domain can play a critical role in ensuring efficient and effective issue resolution in a DevOps environment.

2.  Activating domain separation in a live ServiceNow instance can introduce a number of potential issues, some of which include:

1. Data loss: Domain separation involves creating new tables and modifying existing ones, which can result in the loss of data if the activation process is not properly managed.

2. Performance degradation: The introduction of domains can increase the amount of data stored in the instance, leading to a slower performance.

3. User confusion: Domain separation can create confusion among users who are used to accessing all data in a single instance.

4. Configuration changes: Activating domain separation often requires changes to existing configurations and customizations, which can lead to additional work and potential errors.

To help mitigate these potential issues, ServiceNow provides guidelines and best practices for activating domain separation. Before activating domain separation, it is recommended to carefully review the product documentation, including the Domain Separation Implementation Guide, to ensure a smooth transition. Additionally, a full backup of the instance should be taken before the activation process is started, in case data needs to be restored in the event of an issue.

8 Best Practices for Supporting Domain Separation 

Mark Correct and Helpful if it helps.

[sai12]

Hi,

It actually lies in at build domain which is SDLC component (DEVops) .  this Domain is majorly managed/ contributed by Teams. So the development work/ pipeline work lies in this Domain.

SDLC Component:  Used to track configuration files, microservices, for DevOps

Teams: Developers and IT operators working collaboratively together in order to increase the speed and quality of software deployment

Hope this helps!