Horizonal Discovery Pattern : Identification Engine Payload Sanitization

[tphillips]

I developed a Horizontal Discovery Pattern in Kingston that worked wonderfully. After upgrading to London, it now fails.  I'm noticing a new step in the Payload Processing called "Identification Engine Payload Sanitization".  This step seems to remove items from the payload it deems as duplicates.  In my case, it is using the "Name" field to determine the dups.  However, with this Class I don't do Identification/Remediation on the "Name" field. The "Name" field can be duplicated; however, the MAC Address is always unique.  My pattern fails before it starts the Post Processing steps.

Anyone out there know any info on the "Identification Engine Payload Sanitization" step and how I can work around it?

Thanks,

Tom

[robertgeen · Accepted solution]

What table are you loading data into? You may have to check the identification rule for that table as it's sanitizing based upon that more then likely.

[tphillips]

Robert,

Thanks for the reply and suggestion.  I've looked at the table and don't see where anything in the table would cause it use the "Name" field.

Thanks,

Tom

[tphillips]

Robert,

Update to my issue.  I did end up changing the identification rule for that table.  ServiceNow was never really able to answer the question of why the "Identification Engine Payload Sanitizaiton" step appeared.  After modifying the identification rule, all worked.

Thanks,

Tom

[shubhi]

Hi @tphillips ,

Please confirm the fix.I am also facing similar issue

Thanks

Shubhi Johri