MSFT SQL Instance creating empty records in Servicenow via Discovery

[Garima Tripath1]

Hi All,

For MSFT SQL Instance, I have created two CI Identifiers.

1. Name with Priority 50 

2. Class and Instance name with Priority 100

Now I can see 50 records getting creates where name, and instance name both are empty

both Identifiers have Allow Null Attributes true.

Please let me know what's incorrectly configured in the Identifier which is causing duplicates, the empty records have unique running process parameters.

Add Products

[Patrick Oudsho1]

Hi Garima,

We have the same issue here, no name and instance_name for created MSFT SQL Instances.
This while working with out-of-the-box pattern and identifiers.

When I look closely, it seems all related to SQL Server Express LocalDB and the identifier 'Lightweight identification for MSSQL'.

Initially during debugging I can see both name and instance_name are set, but they seem to get lost along the way. When I look at the result of my discovery in the JSON-file found in the ECCQueue record I see no name and instance_name anymore.

So I am going to raise an incident with ServiceNow, since it seems something fails out-of-the-box and has nothing to do with how you set it up.

Just my 2 cents.

Cheers, Patrick

p.s. I also noticed in debugging that the discovery_source is hardcoded set to 'CredentiallessDiscovery' and am wondering if this is related to the issue. Although also this value is lost later on if you check the ECCQueue record you get back.

[Mari Gran]

Hi Patrick,

Have you been able to get a response or solution to this please? We appear to be seeing the same issue.

Thanks

[KrystianS]

Hi @Patrick Oudsho1 
Did support help you?

[a_mirosavljevic]

I have noticed the same issue when troubleshooting "Lightweight identification for MSSQL".
In the pattern payload , the "instance_name" value is collected but disappears somehow later. 
I still didn't find the reason besides that.