Need data re-classification to granular classes of cmdb_ci_hardware table.

[KunalVerma]

Hi Folks,

Greeting for the day.

I have done ServiceNow and LogicMonitor inbound integration using a store app called 'LogicMonitor CMDB integration' plugin. I am able to receive 5.5k data in ServiceNow cmdb_ci_hardware table from LogicMonitor server. But the incoming data is getting bombarded into cmdb_ci_hardware table instead I want it to be re-classifiied into granular classes (Ex- Server, Computer etc). From LogicMonitor not getting any attribute which define it's class. 

Note : I didn't get help from ServiceNow HI support as it's a third party application.

Link to plugin - ServiceNow Store - LogicMonitor CMDB Integration

Really appreciate your elaborated guideance as I'm bit new to this ITOM field.

Will wait for your acknowledgement at the earliest.

Thanks a lot in advance.

[KunalVerma]

Hi All,

Did any one get a chance to face similar issue where the data is coming from LogicMonitor server to serviceNow table (cmdb_ci_hardware). But the data is not getting classified to extended child tables like Server, computers etc.

Please share your thought on this issue.

Thanks in advance.

[Mio Matsushita]

Hi @KunalVerma !

I have no experience with the 'LogicMonitor CMDB integration' plugin, but I can provide information on two approaches.

The first is to customize the plugin import process.
Modify the third-party plugin import process to identify the correct CI class.
In some cases, ask the provider of the third-party plugin.

Second, configure reclassification during the Indentification and Reconciliation (IRE) process in the CMDB.
Try importing after reclassification is enabled.
https://docs.servicenow.com/csh?topicname=c_CIReclassification.html&version=latest

You can also manually reclassify (downgrade) CI classes, although this is not a radical solution.
https://docs.servicenow.com/csh?topicname=t_ManuallyReclassifyCI.html&version=latest

[Ayda Abdullah]

Hi,

I'm encountering the same issue. Did you manage to resolve it, if so please advise

Issue: The import is missing the sn.sys_class_name attribute, which determines the class in which the CI should be created. As a result, it's defaulting to the cmdb_ci_hardware class, as specified by the system property: x_lomo_lmcmdbint.logicmonitor.class.default

Thanks in advance

[Ayda Abdullah]

Hi, I contacted LogicMonitor directly and this is their response:

"To answer your question, the app defaults to hardware and the mapping is done through the scoped application components. Class name being populated before import requires that the class is defined as a custom property in LogicMonitor on the resource which does not come out of the box when adding them/needs to be included during onboarding or manually added (or automatically added via the integration once the mapping is done on the ServiceNow side)."

I'd say the quickest way to fix is have the custom attribute sn.sys_class_name added in LogicMonitor