Agents Administration - Tests
 

Default Parameters for AzrBillingTest

This test reveals how much the monitored subscription has been billed for in the current month. Detailed diagnosis provides the meter-wise break-up of the bill cost, along with the usage quantity. Meters are used to track a resource's usage throughout its lifetime. When you create a single Azure resource, like a virtual machine, it has one or more meter instances created. Meterlevel insights lead you to the exact meter instances that contributed to the abnormal cloud spend (if any).

Additionally, the test also reports the total count of resources, resource groups, services, tags, and regions used by the target subscription. Detailed diagnostics reveal the exact names of the entities (i.e, resources, resource groups, services etc.) consumed and the pre-tax cost per entity. If a subscription's usage is abnormally high in any month, then this entity-level visibility will pinpoint which specific entities contributed to it.

This page depicts the default parameters that need to be configured for the AzrBillingTest.

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • Specify the GUID which uniquely identifies the Microsoft Azure Subscription to be monitored in the SUBSCRIPTION ID text box.To know the ID that maps to the target subscription, click here.

  • Specify the Directory ID of the Azure AD tenant to which the target subscription belongs in the TENANT ID text box. To know how to determine the Directory ID/Tenant ID, click here.

  • The eG agent communicates with the target Microsoft Azure Subscrption using Java API calls. To collect the required metrics, the eG agent requires an Access token in the form of an Application ID and the client secret value.Specify the Application ID of the created Application in the CLIENT ID text box. To know how to determine the Application ID ,click here. Specify the client secret value in the CLIENT PASSWORD text box. To obtain the client secret value, click here.

  • Confirm the CLIENT PASSWORD by retyping it in the CONFIRM PASSWORD text box.

  • In some environments, all communication with the Azure cloud be routed through a proxy server. In such environments, you should make sure that the eG agent connects to the cloud via the proxy server and collects metrics. To enable metrics collection via a proxy, specify the IP address of the proxy server and the port at which the server listens against the PROXY HOST and PROXY PORT parameters. By default, these parameters are set to none , indicating that the eG agent is not configured to communicate via a proxy, by default.

  • If the proxy server requires authentication, then, specify a valid proxy user name and password in the PROXY USERNAME and PROXY PASSWORD parameters, respectively. Then, confirm the password by retyping it in the CONFIRM PASSWORD text box.

  • The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.