CMDB Sync - Attributes Sync per ci class

Question

Hallo&nbsp;This is more of a PowerFlow discussion on the CMDB Sync pack. Currently the mapping of attributes is not restricting on what class have what attributes. It is mostly coming down to what we currently have it map within ScienceLogic. The fun of that is that the PF will come down to some weird attributes association with different class, even when that attributes does not exist. Example Blade and CPU counts are certainly not an attributes of wap_network Ci class, however PF will put that together and make the payload a bit bigger and send over to ServiceNow. Then it gets ignored. While that we also cannot see the Ignore on the PF Debug.{&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"className":"cmdb_ci_wap_network",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"values":{&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "x_sclo_scilogic_monitored":true,&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "x_sclo_scilogic_id":"123456",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "x_sclo_scilogic_region":"ScienceLogic",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "x_sclo_scilogic_url":"https://support.sciencelogic.net/em7/index.em7?exec=device_summary&amp;did=123456",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "object_id":"BR_1_AP",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "company":"a9b548781be235496287bc4bcb4bcb04",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "sys_domain":"3d854c381be230502c496287bc4bcbd3",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "short_description":"Description: Fortinet.AccessPoint, Device Class: Fortinet | FortiAP",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "u_public_ip_address":"10.11.10.4",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "u_operation_state":"connected",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "serial_number":"FP432FTF000000001",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "u_software_version":"FP432F-v7.4-build0540",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "version":"FP432F-v7.4-build0540",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "u_uuid":"f039250e-4878-51ef-42f2-f0b32e139f7d",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "cpu_count":0,&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "cpu_speed":0,&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "first_discovered":"2025-01-23 19:11:03",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "firmware_version":"FP432F-v7.4-build0540",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "u_firmware_version":"FP432F-v7.4-build0540",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "os":"FP432F-v7.4-build0540",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "fqdn":"BR_1_AP",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "host_name":"BR_1_AP",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "u_discovered_manufacturer":"Fortinet",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "manufacture":"Fortinet",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "u_discovered_model_number":"432F",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "model":"432F",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "model number":"432F",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "name":"BR_1_AP",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "blade_serial_number":"FP432FTF000000001",&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "cost":0&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;},

apurvabirala · Answer

kenwu Trying to understand - Is the concern here the payload size? Wondering if the unwanted attributes are coming in the way of sync, extending the time of the sync, etc.

saraleslieadmin · Answer

Thanks for your post, I have reached out internally for some feedback here.&nbsp;
Thanks, Sara&nbsp;

kenwu · Answer

HI Apurva,&nbsp;There are 2 things that is discussed here.What are the attributes that we are sending to ServiceNow, the example above, provide 8 attributes that will get ignore by ServiceNow. as per Cpu / software / serial numberAs the above payload for 1 Ci, we have 30 attributes while that minimally, 8 of them are ignored by ServiceNow, as they are mapped as they are available in SL/PF. That's nearly 25% of payload.&nbsp;&nbsp;When we are synching 80K devices, that will change the payload size and wait time.&nbsp;&nbsp;

Forum Discussion

CMDB Sync - Attributes Sync per ci class

Related Content

GQL queries with attributes

Azure monitoring and integration with CMDB

ServiceNow CMDB v3.6.2 SyncPack

ServiceNow CMDB SyncPack v3.6.1

Re: Provisioning a Virtual Device in SL1 API

Recent Discussions

Can't get new device icon to show

Device Deletion Audit Report

SNMP catching for non Snippet DA

Bandwidth reports

ScienceLogic - ServiceNow Integrations: ITOM Licensing Requirements