Reduced licensing usage counts when multiple discovery mechanisms discover the same CIs - Known Error

Reduced licensing usage counts when multiple discovery mechanisms discover the same CIs Description When a discovery mechanism discovers a CI (such as a virtual server) the discovery_source field in the CI contains the name of the mechanism/integration that discovered the CI. This attribute is used by the licensing process to calculate how many units are being consumed by the customer and if the usage is within the bounds of the license terms.

When an instance is configured with multiple discovery mechanisms (ServiceNow Discovery, Tanium, etc) the discovery_source field will be overwritten every time a discovery mechanism executes. If a server is discovered by ServiceNow and then a Tanium discovery schedule finds the same CI, the discovery_source field will be overwritten. The licensing process will not consider this server for the usage calculation. This will cause the licensing reports to undercount the actual usage.

Steps to Reproduce

Setup ServiceNow Discovery.

Configure and run a schedule to discover servers.

Setup an alternate discovery mechanism like Tanium.

Execute the alternate discovery mechanism.

Workaround This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, check the Fixed In field to determine whether any versions have a permanent fix.