Getting Started with Azure Monitoring via AIMS
Since a couple of weeks I’m part of the AIMS Performance Pro team because of my knowledge on Azure and other related topics. The AIMS performance Pro team (#aimsperformancepro) is a program for ambitious and outspoken technical professionals who have interests in the intersection of IT integration, monitoring, analytics, performance tuning and troubleshooting.
It is a great honor for me to be part of the team, but I also want to add that you do not get sales talk about AIMS. In all my post I will give my own opinion both good or bad.
To give a clear opinion I started to try out the monitoring solution of AIMS for Azure. This blog post will get you up and running and in the future I will publish other post on what I discover with AIMS.
But what is so special about the monitoring solution of AIMS. Here is what they mention on their website.
AIMS it is the only performance monitoring and governance solution that applies AI and machine learning to give you complete control over your Azure environment. With AIMS, you can automatically detect anomalies in your Azure Services, correlate issues across cloud and on-prem environments and actively control your Azure consumption costs.AIMS
On the website you can also see which Azure Services they currently (01-2019) monitor:
- Azure Web Apps
- API Management
- Virtual Machines: Classic Compute
- Network/Network Interfaces
- Virtual Machines: Compute/Disks
- Network/Public IP Addresses
- Cosmos DB
- Virtual Machines: Compute/VMs
- Event Hub
- Key Vault
- Logic Apps
- Azure Billing Data
- Service Bus
- Signal R Service
- Azure SQL DB
- Azure Storage
- App Service Plans
- Azure Functions
This requires a test-drive in my opinion.
To get started you will need a service principal in Azure Active Directory for AIMS to read all the information within your Azure Subscription. In this blog series we will give this service principal “Reader” rights on a management group that contains all my subscriptions. Because I want to monitor all my subscriptions.
- Open the Azure Portal (https://portal.azure.com)
- Go to Azure Active Directory.
- Click on “App Registrations” and click on “New Application Registration”
- Fill in a name for the application. You could use “AIMS Monitoring Application” and set the type to “Web App / API” and fill in a random URL.
- When the application is created the application blade will be shown. From this blade copy the “Application ID” to a notepad for later use.
- Click on “Settings” and then “Keys” and add a new key. Copy this key for later use.
Access within Azure
As mentioned before the application needs the “Reader” role within the subscription. As I have multiple subscriptions I have a management group that contains all of my subscriptions. To configure the “Reader” role on all subscriptions:
- Open the “Management Groups” blade. (All services > Management Groups)
- Select the correct Management Group and in the management group click on “details”.
- In the details blade click on “Access Controls” and then “Role Assignments”. Click on “add role assignment” to add a specific role assignment.
- Within the role assignments blade select the appropriate role and application.
With the application configured we can add a subscription to an AIMS environment. To test this all out I requested a test environment from AIMS via the following link https://www.aims.ai/aims-free-edition. If you already have an account use this URL to login https://login.aimsinnovation.com/environments.
When you have the environment and also created a environment in there you are able to set it up for monitoring your subscription.
- In your AIMS environment open the menu by clicking the gear icon.
- In the menu click on “Agents”
- On this page all of the already configured agents shown. Click on “Connect Agent” to add a new agent (subscription).
- In the connect agent window make sure you select the “Azure agent” as your agent type and supply all the information of your subscription and of the newly created service principal and click on “Create” to start monitoring your subscription.
If you configured everything correctly information about your subscription will be retrieved and added to the portal. This can be checked by going to the “Topology” tab. In this tab you should see resource group names that are in the subscription. (Be patient it can sometimes take a while. The first time it took me about 5 minutes).
With the agent configured I’m really curious of what the system can do for me. In future post I will keep you updated of some of the features and my findings regarding the solution.