Has anyone else had issues with the complex and confusing logic used to calculate ITOM SU's?

[eta0725]

Anyone experiencing issues with in cluster Kubernetes discovery creating K8 Nodes and Linux servers that lack relationships, while cloud account based discovery creates Virtual Machine Instances also representing scale set K8 nodes?  

Or Azure VDIs that are managed through Citrix DaaS that lack the metadata that ServiceNow uses for exceptions on end user compute? 

Possibly, any other easter eggs that may contribute to inaccurate counting of SU's for ITOM? 

Thanks in advance for any insight or feedback! 

[vish_1111]

We are...

[Ram Devanathan1]

We have fixes for the issue with VDI VMs getting counted. pl contact support. email me ram<at>servicenow<dot>com with the case number.

in general for doubts about cloud licenses, or if you need help with cloud SU's estimation - please activate cloud license estimator tool in your sub-prod instance. this tool is available in innovation labs (pre-release tech preview). we will also improve this tool to ignore VDI instances.

Ram

Products Director, ITOM

[eta0725]

Thank you, Ram.   I emailed you directly with some additional questions.  I look forward to trying CLE to see if it will help us estimate SU increases in the future.