Service Mapping License query
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2020 08:49 AM
Looking for a query to determine the license count for Service Mapping. I know under Service Mapping, we can list the CI and filter on the server classes. The query looks for sys id is one of javascript:saListCis ('XXXXX')
However, I am looking for a query to get the overall count including all the Service Map in the system, so that we can dynamically manage our license count for Service Mapping.
- Labels:
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2020 02:06 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2020 07:13 AM
License Summary is just showing the Purchased number and when it expires and not any used count. We want to know how many licenses have been consumed by Service Mapping so far. For e.g. for Discovery, we have a query on cmdb_ci_server where most recent discovery is not empty and discovery source is ServiceNow.
What is the corresponding query for Service Mapping? I understand it is Service Mapping is also license by node but we dont know the query parameter.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2020 04:34 AM
Hi Sachin,
If you're subscribed to ITOM Visibility your SU (Subscription Units) for Discovery and Service Map should be one and the same thing. This is from the pricing model this week as I had a similar query for the sales team I work with, your mileage may vary so do check this is the agreement in place within your organisation but hopefully it's a start.
Includes former Discovery and Service Mapping applications now as features of ITOM Visibility. Customers may use any or all features of ITOM Visibility on a given IT resource and only consume 1 SU (or fraction thereof, depending on the resource type: SU ratio).
ITOM Visibility is subscribed based on the average of the last 90 daily counts of resources of types defined in the SU ratios list. Each daily count measures the number of applicable resources currently being managed by ITOM Visibility (i.e. the CI has not been marked as Retired, Absent or Stolen).
For reference, the SU ratios are defined as below.
- 1 Server = 1 SU
- 3 PaaS resources = 1 SU
- 3 Containers = 1 SU
- 1 Unresolved Monitored Object = 1 SU
And the classes are below, starting with Servers.
- cmdb_ci_server
- cmdb_ci_vm_instance
- cmdb_ci_ucs_rack_unit
- cmdb_ci_ucs_blade
- cmdb_ci_mainframe_hardware
- Any subclasses of the above listed classes
Here are the classes for Containers.
- cmdb_ci_oslv_container
- Any subclasses of the above class
And here are the classes for PaaS.
- cmdb_ci_cloud_appserver
- cmdb_ci_cloud_database
- cmdb_ci_dynamodb_table
- cmdb_ci_cloud_directory
- cmdb_ci_cloud_function
- cmdb_ci_cloud_gateway
- cmdb_ci_cloud_messaging_service
- cmdb_ci_cloud_webserver
- Any subclasses of the above listed classes
Hopefully that helps you get some filter in place.
Cheers,
Sam