CMDB Query Builder - Technical Service Offering

CW7
Tera Contributor

Hi,

I am trying to use the CMDB Query builder to create a dynamic query that can be used in a Technical Service Offering.

The logic includes 2 CI classes; Server and MSFT SQL Instance. I am trying to create Technical service offerings for the the different environments and apply to the DB Instance. eg SQL Prod, SQL Test, SQL Dev. These can then have different criticality, support team, etc...

The logic relies on the environment of the server. If the server has a production environment then so will the database instance that runs on that server...

I have created the query however the results cannot be configured to exclude the servers and so cannot be used in in a dynamic CI group. The servers are part of another service offering and are supported by windows platform teams so I dont want to include them. I only want the instances.

 

The server is required for the logic to work in the query but should not be in the output, I only want the DB instances. 

1 ACCEPTED SOLUTION

This is just how the Dynamic CI Groups/CMDB Groups work.  They take ALL of the CIs returned in the Saved Query.  For CMDB Groups created with standard filters (which is a common use case) you look for a specific set of CIs of a specified class that meet certain conditions.  However, if you use a Saved Query to populate your CMDB Group, then it will include all of the CIs that are in that query.


The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.

View solution in original post

15 REPLIES 15

I see both potential scenarios.  I think the "idea" that I would post (if I had access to post ideas, <ahem>) would be to add the ability to define a CMDB Group using the intersection (not the union) of two or more queries, or to just exclude certain query nodes from the actual results.

 

While in some cases I might want to use the query relationships to identify certain nodes, and ignore the nodes that I used to perform the query itself, in other cases it does make sense to include all of the nodes in the query.  I think this would be a great feature to add to CMDB Query Builder.


The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.