What is Dynamic CI Group

[miyu]

Please tell me what I can do by creating a Dynamic CI Group, I am confused as to the use of a Dynamic CI Group and how it differs from a CMDB Group.

[Amit2023]

If assignment group is modified at CI level then does it get overruled by the assignment group value set at DCG level ?

[CMDB Whisperer]

Not sure off the top of my head but it should be easy to test.  If I had to guess from what I have seen elsewhere (e.g. with the Managed by Group field) I would guess that the Service Offering / DCG assigned groups will overwrite the CI groups when changed, but that you may then override them again on the CI level.  Not that this is how it should work, just my guess at how it does work.

[Anish Reghu]

Hi Paul,

Please correct me if I am wrong - By "cascading the group assignment to individual CIs" - You mean to say that it helps to fill in the Support group information on the CI thereby helping the incidents or change requests where the CI is being referenced. Did I understand that correct?

Regards,

Anish

[AishwaryaS1]

@CMDB Whisperer 
I've requirement in which I wanted to update the support group, change group, managed by group, approval group. There are some specific groups only that I need to update not for all.
I found One of the Business Rule and Scheduled Job Script which is updating the groups
I've question whether this script is only updating the Dynamic CI group Class Records or all the other class records.
one more When I open cmdb_ci table I found all those records of having class Dynamic CI Group, Application Service, Linux Server where I've to update the groups, So if I update the records from cmdb_ci_table will it be override by scheduled job script or not.

[DUGGI]

Let's say you have a large number of servers in your CMDB and you want to monitor the health of all the servers that have critical or high priority incidents associated with them. One way to do this would be to create a CMDB Group and manually add all the servers with critical or high priority incidents to the group. However, this would be time-consuming and you would have to keep adding and removing servers from the group as incidents are resolved or new ones are opened.

Instead, you can create a Dynamic CI Group based on a dynamic set of criteria. For example, you can create a Dynamic CI Group that includes all the servers in the CMDB that have critical or high priority incidents associated with them. To do this, you would create a query that searches for all servers in the CMDB that have incidents with a priority of critical or high. The query would look something like this:

Table: cmdb_ci_server
Query: incident_priority IN [1,2]

This query would return all the servers in the CMDB that have incidents with a priority of 1 (critical) or 2 (high).

Once you have created the Dynamic CI Group, you can use it to monitor the health of the servers that meet the specified criteria. For example, you can create a dashboard that displays the status of all the servers in the group, or you can create a report that shows the number of incidents associated with each server in the group.

The main advantage of using a Dynamic CI Group in this scenario is that the group membership is always up-to-date with the latest CMDB data. As new incidents are opened or resolved, the membership of the group automatically updates to reflect the changes. This saves time and reduces the risk of errors that can occur when manually updating CMDB Groups.

Overall, Dynamic CI Groups can be a powerful tool for organizing and managing large numbers of CIs in the CMDB based on dynamic criteria, providing a more efficient and effective way to manage your CMDB data.