The eG agent collects metrics from the target Microsoft azure cloud in an agentless manner only.


eG two deployment model for Azure:

  • ARM Model(Azure resource Model)
  • Classic Model

Monitoring the Microsoft Azure (ARM) : 

In order to collect metrics from the Microsoft azure cloud, eG agent communicates with the target Microsoft azure cloud using Java API calls. To collect required metrics, eG agent requires the following:

  • Directory ID of the target Microsoft Azure cloud
  • Access token in the form of an Application ID and Key

Directory ID of the target Microsoft Azure cloud :- (TENANT ID in eG)

 Click on Azure Active Directory -> Properties -> Directory ID



Directory ID:-  6db39cb1-dc8b-4c57-a45f-3107fac4c946

Create a Web Application in the Active Directory of the target Microsoft Azure.


Access token in the form of an Application ID and Key :- (Client ID and Client Password in eG)

Click on Azure Active Directory -> App Registeration -> Click on + New Application Registration -> give the Name of the application , Application Type , Sign-on URL




You can find the Application ID in the below screenshot.



To generate the Key (Client PWD) click on Settings -> Keys -> update the key name & Duration field and click save.




Associate the Created web application to the Subscription of the Azure Account




eG Interface:

Admin -> Add/modify components -> Microsoft Azure -> Provide any name in the Host/ip & Nickname field.




Configuration:

Provide :-

  • Tenant ID ( Directory ID)
  • Client ID (Application ID)
  • Client PWD (Key)




Azure Classic Model:-

In order to configure and monitor Azure Classic Model in eG, we need the following information and criteria to be achived:

  • Need the Subscription ID
  • Management certificate need to be associated with the Subscription, Management can be created by Azure or we can create our own Management certificate
    • If we are creating our own Management Certificate, then we need to follow the below-mentioned steps:
      • Step1: Create a KeyStore (in the Collector Box)
      • Step2: Create Management certificate (in the Collector Box)
      • Step3:  Upload the certificate (in the Azure )

      • Step 1: Create a KeyStore:
        • In the Collector Box,  go to C:\eGurkha\java\jre7\bin>keytool -genkeypair -alias <Ip of the remote agent > -keyalg RSA -keystore C:\eGurkha\agent\eG-Azure-Lab.jks -keysize 2048 -storepass "Tot@lperformance"
        • Provide the details given below


                       

  • Step 2: Create Management Certificate:
    • In the Collector Box,  go to C:\eGurkha\java\jre7\bin>keytool -v -export -file C:\eGurkha\agent\eG-Azure-Lab.cer -keystore C:\eGurkha\agent\eG-Azure-Lab.jks -alias 192.168.1.63
    • Certificate will be extracted to the above mentioned location.


  • Step 3:Upload Certificate :
    • Go to Subscription in Azure  -> Click on the specific Subscription
    • Click on Management Certificate -> Upload Certificate (the one that we created)



  • Configuration:


  • Note : Any Test with regard to Azure Classic Model is not enabled Out of the Box.


Step 1: Enable the Test for Azure Classic Model

  • Click on Admin -> Tests -> Enable/Disable -> Choose Microsoft Azure and enable the test.



  • Step2:  Choose one of the test and update the below information:
    • Subscription ID
    • Certificate Path ( Path where the .jks file is)
    • Certificate Password