Agents Administration - Tests
 

Configuration of AzrBillBySrvcTest

Use this test to know the cost of usage of each service that you subscribed to during the current month. Say, the AzrBillBySrvcTest reveals an unusually high cloud spend in the current month. In such a scenario, you can compare the metrics that this test reports across services to accurately identify the service because of which your cloud usage cost for the month may have increased significantly. Additionally, the test also reveals whether you overspent on any service - i.e., whether/not you spent more than you originally budgeted for specific resources in a service. Detailed diagnostics lead you to the exact resources that may inflate the total usage cost of the service in the current month. Using these insights, you can course-correct, so that expenses stay within budget. The insights also help you draw out budgets that are not overly aggressive or ambitious, but are in fact realistic and actually align with real-time cloud usage.

The default parameters associated with this test are:

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

  • In the HOST text box, specify the HOST for which this test is to be configured.

  • 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.

  • If you want to be alerted if the current month's spend on specific resources has exceeded their budget, then configure a comma- separated list of <Resource_ Name>:<Budgeted_ Cost_ in_ USD> pairs in the LIMIT RESOURCE COST text box. For instance, your specification can be: adVM:20,AzureMonitor-Test:12,wvdsprin1:7. This test will then compare the estimated usage cost of the configured resources with the budgeted cost specified here. If the anticipated spend for even one of the configured resources exceeds the specified limit, then the test will report the value Yes for the Are charges exceeding budget? measure, and raise an alert on the same. This way, the test makes sure that you do not spend more than you should on specific resources.

    By default, LIMIT RESOURCE COST parameter is set to none. This means that there is no restriction on how much you can spend on resources. By default therefore, the Are charges exceeding budget? measure reports the value No.

  • 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.

  • To make diagnosis more efficient and accurate, eG embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability.

    • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button will allow you to apply the configuration to all/selected components of that type.

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

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.