Foglight Hybrid Cloud Manager 7.3.0 - User Guide (for Azure environments)

API used to collect Cost metrics

Foglight Hybrid Cloud Manager for Azure offers the following two methods to collect Cost metrics, you need to select either of following based upon your environment:


	TIP: For the detailed information about how to get the subscription type, see To get the subscription information:.

•

Enterprise Agreement Billing API: This approach is used to collect metrics from Enterprise Agreement subscriptions.

•

Usage API and Rate Card API: This approach is used to collect metrics from Pay As You Go subscriptions and Azure In-Open subscriptions.

If you use Enterprise Agreement API to collect Cost Metrics, You need the Enrollment Number and API access key associated with your Azure Enterprise account. You can locate these credentials in your Azure Enterprise account. The Enrollment Number and API access key are available only to your account's enterprise administrator, the top-level administrator of your Azure Enterprise.:


	NOTE: Enterprise Agreement Billing API only applies to Enterprise Agreement subscriptions and collects cost metrics directly from the Azure Enterprise Portal. If not, Foglight Hybrid Cloud Manager will use Usage and Rate Card APIs to collect and populate the cost data for subscriptions.

•

Enrollment Number: Indicates the master account used for Enterprise billing.

•

Usage API Access Key: Allows access to the Azure Billing API.

•

Offer ID and Billing Cycle day for Subscriptions: Specifies the subscriptions type and information.

To get the Enrollment Number and Usage API Access Key:

Locate your Enrollment Number.

Click the Enrollment tab, then click Manage.

Locate the Enrollment Number in the list of enrollment details.

Copy the Enrollment Number and save it for later use.

Generate an API access key.

Under the Enrollment tab, click Reports.

Click Download Usage.

Click API Access Key.

Click the key icon in the Primary Key text box to generate the API access key.

Copy the entire API access key string into a text file, and save the file.

To get the subscription information:

Click All services, and then input “Subscriptions” in the All services text box, and then click Subscriptions.

On the Subscriptions dashboard, select your subscription, and then record the following information:

•

Offer: This value indicates the subscription type, for example, Pay As You Go.

•

Current billing period: This value is used to set the Billing Cycle Day in Editing agent properties. For example, your Current billing period is “6/21/2018-7/20/2018”, then the Billing Cycle Day will be “21”.

Azure monitoring setup

To fully enable the monitoring of Azure environment, Foglight Hybrid Cloud Manager for Azure requires to create an Azure Performance Agent that is to be authenticated using Azure Active Directory ID (Tenant ID), Application ID, and Access Key.

A complete setup includes the following three steps:

Get the authentication information through the Azure portal. For more information, see Getting authentication information through Azure portal.

Create an Azure Performance Agent on the Foglight Management Server. For more information, see Creating Azure Performance Agent.

If your Azure Performance Agent is installed behind a firewall, configure firewall settings on the machine running the Foglight Agent Manager. For more information, see Configuring firewall settings.

Getting authentication information through Azure portal

To get Tenant ID, Application ID, and Access Key through the Azure portal:

On the left navigation panel, select Azure Active Directory.

The Azure Active Directory view that belongs to your account opens.

In the Azure Active Directory view, select Manage > Properties, and then click

to copy the Directory ID, that is also known as Tenant ID.

In the Azure Active Directory view, select Manage > App registrations, and then click New registration.

The Register an application view opens.

Type the following information, as needed, and then click Register.

•

Name: type the name of the application.

•

Supported account types: select who can use this application or access this API.

•

Redirect URL (optional): type the URL address where users can sign in and use the application.

The Register an application view closes and the App registrations list is refreshed automatically.

In the App registrations list, select the application created in Step 5.

Keep the Application ID displayed in the Application details view somewhere safe.

In the Application details view, click Manage > Certificates & secrets. The Certificates & secrets view opens on the right.

In the Certificates & secrets view, click + New client secret.

The Add a client secret view opens.

In the Add a client secret view, specify the values of DESCRIPTION and EXPIRES, and then click Add.

Click

to copy the key value.

Click Microsoft Azure on the top left corner, to return the default dashboard that appears once logged into the Azure portal.

On the left navigation panel, click Subscriptions.

The Subscriptions view opens.

In the Subscriptions view, click the subscription that you want to monitor, then the Subscriptions details view opens.

In the Subscription details view, click Access control (IAM), then Access control (IAM) view opens on the right.

Click Add and select Add role assignment. The Add role assignment view opens.

In the Add role assignment view, select Reader from the Role drop-down list, search for the application created in Step 5, and then click Save.

Repeat Step 11 to Step 16, to assign the Storage Account Key Operator Service Role to the application created in Step 5.

NOTE: Repeat this procedure if there are multiple applications to be monitored.


	NOTE: Diagnostics settings must be enabled to collect metrics for both ARM-deployed virtual machines and standard Storage Account. For more information, see How to enable metrics using the Azure portal. NOTE: For Linux instances only, please install Python 2. For more information, please see Linux Diagnostic extension to monitor metrics and logs article https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/diagnostics-linux-v3#prerequisites that explains the Python requirement.