How to deploy usage_metering and billing probes in different types of environments

Document ID : KB000034709
Last Modified Date : 14/02/2018
Show Technical Document Details


Deployment Guide

For the link below, you will see that you normally only need one usage_metering and billing probe. if you are dealing with an MSP environment, refer to Scenario 2.

Primary and Secondary Instances
The usage_metering probe needs to perform DNS resolution to uniquely identify a probe's device references. In many cases, the DNS needed to correctly resolve a device reference is not available in/from the main (primary) location where a single usage_metering instance is running.

To address this issue, a secondary instance of usage_metering can be installed to a hub having access to a DNS that can correctly resolve device references contained in that hub's robot probes. Note that only the hub robot and all its 'children' robots are analyzed in a secondary instance scan.

*For more detailed information please refer to the link referenced above.

See also: "Deployment Scenarios" at the link above for deploying within Enterprise (self-contained environments) versus MSP environments.

keywords: billing types environment environments usage usage_metering hot deployment deplyments secondary remote hub hubs need more than one multiple subscription file files


// https