Discovery and CI Identifier for MSSQL instances

[klautrup]

Hi,
We want to ensure new Server CIs and DB Instance CIs are created manually and then afterwards when deployed enriched by Discovery.

For Server CIs Discovery uses the ootb CI Identifier "Hardware Rule" which ensures a match on 'name' thus Discovery merges with the manually created Server CI with that same name.

However, for MSSQL instances in MSFT SQL Instances (cmdb_ci_db_mssql_instance) all though there is an ootb CI Identifer "MS SQL server" matching on sys_class_name + instance_name:

Discovery does not merge with a manually created CI in that table all though there is a match on field instance_name.
Instead Discovery creates a duplicate CI and relates that as Runs On to the Server CI and Contains to the Database CIs:

In the CI Identifier I tried adding a match on the 'Name' field with higher priority:

But same result Discovery creates a duplicate.

How do I get Discovery to match with manually created SQL Instance CIs?

[klautrup]

Thank you all for the quick solution.

I actually already tried doing the Runs On relation to the server CI.
However, when I tested that I missed that the default identification rule uses the instance_name field instance of the name field and since I had only populated the name field it still created a duplicate.

However, re-testing with the Runs On relation to the Server CI and having the instance_name field populated Discovery nicely merges with the manually created instance CI 🙂

[robertgeen]

Great to hear. Thanks.