|
Default Parameters for 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.
This page depicts the default parameters that need to be configured for the AzrBillBySrvcTest.
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.
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.
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.
|