ServiceGraph connector For SolarWinds - Change Class Name

Gayan Udayakant
Tera Expert

‎11-09-2023 07:59 PM

Recently we have installed the ServiceGraph connector for SolarWinds in one of our client environments and retrieved the Orion Data to the ServiceNow CMDB instance. We have used default data sources and added 2 customer fields to current data sources and it worked perfectly.

 

Somehow we notified in the ServiceNow data in the Network Gear table, that some of the data the class name changed to computer and automatically created the assets as well.

 

However this did not impact all data in the Network Gear table, some of the data class name has been changed to the Computer table.

We have analyzed the Audit log and notified it that it created assets as well.

 

We have reproduced the process manually deleted the Assets for the changed record and changed the Class name as to the previous one. Again we run the scheduler and notify it changes to Computer class for that data only.

 

Please share your experiences

0 Helpfuls
  • 549 Views
2 REPLIES 2

Prabhjyot Sing1
Mega Guru

‎11-09-2023 11:14 PM

Hi @Gayan Udayakant ,

 

I did not fully understand your question here but if you want to know why the asset records are getting created for your CI that is because of an OOTB Async scheduled job that runs to create the asset records when a CI is created, named - "Asset - Create asset delayed sync".

 

What I understand is that your CI is getting reclassified from being a network gear to a computer is that correct?

If so then you have to check the ETL to find out why that is happening, also attaching document for CI re-classification.

https://docs.servicenow.com/en-US/bundle/vancouver-servicenow-platform/page/product/configuration-ma....

 

Regards,

Prabhjyot

 

0 Helpfuls

EkkaluriV
Tera Contributor

yesterday

Hi @ayan Udayakant ,

 

I hope you’re doing well. I wanted to reach out because we’re currently encountering an issue similar to one  regarding CI classification, and I’m hoping you might be able to share how you resolved it. In our environment, several IP Switch Configuration Items are being incorrectly classified under the Computer class instead of the appropriate Network Switch.

If you’ve already resolved this on your side, could you please share:

  • What the root cause was in your case

  • Whether the fix involved changes in ServiceNow (classification rules, IRE, transform maps, etc.) or on the SolarWinds/source side

  • Any specific configuration updates or best practices you recommend

Your insights would be extremely helpful for us and likely for others who might face the same issue. Thanks in advance for your time and support!

 

Thanks

Vijaya

0 Helpfuls