ITOM licensing by CI types

[ajaypradeepsb]

I tried pulling the CI records that would be contributing/responsible for the ITOM license count. But the CI report extract is not matching the license count.

I queried on cmdb_ci_server and cmdb_ci_vm_instance table based on the below condition.

duplicate_of = ISEMPTY

last_discovered = Last 90 days

install_status (NOT IN) Absent, Retired, Stolen

discovery source = ServiceNow, ServiceWatch

By the way, other tables like cmdb_ci_mainframe_hardware, cmdb_ci_ucs_rack_unit and cmdb_ci_ucs_blade that are categorized under CI category doesn't have any records. 

When I combine the records from different class and remove the duplicates by name, I still fall short of around 1000 records to match the count.

Am I missing any tables here? or Am I doing anything wrong or missing something?

I appreciate any suggestion here. Thank you.

. 

[carl_hensley1]

Check table em_unique_nodes, where the "type" is "unknown"

If a EM raises a event, and the CI in the event does not exist in ServiceNow it will create a CI in the system, given SN does not know the class for the CI, it auto assumes this CI will consume a ITOM device license.  So make sure your CMDB is mature enough, and has all the CI's for the events raised.

These can also be populated by Performance Analytics

See:

https://docs.servicenow.com/bundle/london-it-operations-management/page/product/event-management/task/license-usage.html

“Unresolved Monitored Object” is any IT Resource for which the ITOM Health Application receives an event or performance metric which is not represented as a CI in a CMDB table. Unresolved Monitored Objects are recorded in the “em_unique_nodes” table with the “type” field equal to “unknown”.

See: https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/it-operations-management-itom-servicenow-subscription-unit-overview.pdf  (page 3)

[Rahul Priyadars]

This is how it goes-

The Event Management - Node Count job calculates the number of unique nodes that send event information, either directly or through third-parties, to Event Management and are eligible for licensing in the last year. The information from this job is stored in the License Usage [em_unique_nodes] table for visibility by all users. All nodes that send event information are counted, whether the alert generated from the event was bound to a CI or not.

ITOM Visibility

The ServiceNow® ITOM Visibility product consists of the ServiceNow® Discovery feature and the ServiceNow® Service Mapping feature, which together give you a unified, connected view of your entire IT network and the services it supports. For licensing purposes, ITOM Visibility provides the count of CIs that it discovers, both during horizontal and top-down discovery. ITOM Visibility reports the count for CIs of the following CI categories: Servers, PaaS, and Containers.

Hope This helps.

Regards

RP

[Hellfried]

But if a node without a CI (e.g. a newly installed server) that sent this event is discovered a bit later, it will count as 2 licenses, right? Because they are not reconciliated later?