Discovery source and Discovery Dashboard report

[Gaetano De Mitr]

Hi guys,
I have a problem with the CI Discovery source field.
Practically when a record is created by Discovery the field is populated with the value "ServiceNow", while in the case in which it is populated or updated by an external Data source, it is populated based on the name of the external DataSource for example "ExternalSystem".
Unfortunately this generates problems for the Discovery Dashboard which goes to show all the ICs with discovery source = ServiceNow, so in the case, for example, I create a Server from Discovery and subsequently modify the record by mapping other fields, the Discovery Source changes and I no longer see the records in the report.

Obviously I am creating Reconciliation Definitions to manage the priority of updating the fields, so I need this difference.

Is it possible to make the external Data Source modify the fields on which I give precedence without modifying the Discovery Source field? Also, would the reconciliation rules work?

[adilrathore]

I believe you need to write a scheduled job or BR to achieve this, as I think that the JSON which would be constructed for updating the CI with discovery ExternalSystem, would have discovery_source mentioned as ExternalSystem and as such difficult to change.

[Gaetano De Mitr]

How can I know if the specific Configuration Item was discovered by ServiceNow discovery?

I would like to avoid checking through the audit.

[Gaetano De Mitr]

Moreover,

When I call the endpoint to create or update CI, the ServiceNow WS answer me with this response:

{

"import_set": "ISET0010004",

"staging_table": "u_cmdb_external_server_staging",

"result": [

        {

"transform_map": "ExternalServer",

"table": "cmdb_ci_server",

"status": "error",

"error_message": "Target record not found",

"status_message": "Row transform ignored by onBefore script"

        }

    ]

}

whit the same import_set number and same error, but the CI is correctly created or update based on Identification and Reconciliation rule configurated.

[Andrew Westerv4]

Once your CMDB starts to become the data aggregation from multiple sources, it starts to become impractical to report on where a CI came from and is more of a question of what updated it last. The simple answer is to update the OOB reports for the dashboard with removing the Discovery source condition and instead group by that field. That way your bars would show which data source last updated each class.

If you need to know specifically CIs updated by ServiceNow Discovery, you will need to use the Source [sys_object_source] table to provide those answers. Since it's a system table, you will need to update the system property glide.ui.permitted_tables to do so.