Service Graph Connector for CrowdStrike and the CMDB

JonMS
Tera Expert

Question relates to adding the Service Graph Connector CMDB imports over an existing SCCM Import job we already run.

We've installed the application from the store and have it setup. It is successfully bringing in machine records and updating existing records. Is there a way that we can control what fields the Connector is allowed to write to?

As of right now we are having some overlap of some fields (ie. Manufacturer, Name, etc.) where we would like to keep the values being brought in by the SCCM Import.

1 ACCEPTED SOLUTION

Jimmy Yuan
ServiceNow Employee
ServiceNow Employee

I think you want to look at Reconciliation rules for the specific class to define the precedence of what data source can write to what attributes.  You can define higher priority for SCCM for those fields and lower priority on the other source (CrowdStrike).

 

View solution in original post

4 REPLIES 4

Jimmy Yuan
ServiceNow Employee
ServiceNow Employee

I think you want to look at Reconciliation rules for the specific class to define the precedence of what data source can write to what attributes.  You can define higher priority for SCCM for those fields and lower priority on the other source (CrowdStrike).

 

JonMS
Tera Expert

Thank you! This is exactly what I was looking for.

hariv
Tera Contributor

@Jimmy Yuan i am using 

Service Graph Connector for CrowdStrike, connection all set, getting the CI as well, but here i need to exclude few data, How to prevent a record from being inserted based on the conditions.

Abhishek gen
Tera Contributor

Hey, Can you share me the link to the Service Graph connector for Crowdstrike SNOW documentation. I am trying to do this config and i am not getting any SNOW docs for this.