Azure Resource Graph

 

Microsoft Azure- Writing Queries and Creating Dashboards using Azure Resource Graph


In this article, we are going to write an azure resource graph queries in azure workbooks and then we will pin it to Azure Dashboards.

Implementation:

Follow the below steps to implement the above problem statement:

Step 1: Login into the Azure Portal.

Step 2: Go to Azure Monitor Service or You can search for the monitor in Search Bar.

Step 3: From the Left-Menu Click on Workbooks.

Step 4: Then Click on + New.

Step 5: Click on + Add

Step 6: Click on Add query

Step 7: In Edit Query item >> Select Data Source, then Select Azure Resource Graph.

Step 8: Then, Select the Scope (Either Single Resource or Subscription or Subscriptions according to your needs)

Step 9: then Select Visualization, this is Optional. By default, it will select Table.

Step 10: then Select Size, this is Optional.  By default, it will select Medium. You can always choose your recommended size.

Step 11: Leave Color palette as auto (this is Advanced for adding colors to Visualization

Step 12: Now Add your Resource Graph Query, then click on Run the Query

Example: 

Azure Resource Graph Query to find the total number of orphaned disks by Subscription.

Resources | where type has “microsoft.compute/disks” | extend diskState = tostring(properties.diskState) | where  diskState == ‘Unattached’ //or managedBy == “” | project DiskName=name, diskState, Owner=managedBy, SubscriptionName, ResourceGroup=resourceGroup, Location=location, Tags=tags | summarize count() by SubscriptionName

Azure Resource Graph Query to find orphaned disks.

Resources | where type has “microsoft.compute/disks” | extend diskState = tostring(properties.diskState) | where  diskState == ‘Unattached’ //or managedBy == “” | project DiskName=name, diskState, Owner=managedBy, SubscriptionName, ResourceGroup=resourceGroup, Location=location, Tags=tags

Step 13: Click on Advanced Settings in the Edit Query item

Step 14: Check the following options Always show the pin icon on this step, Show refresh icon when not editing, Show Export to Excel button when not editing.

Provide the Chart Title and Click on Done Editing:

Step 15: Click on Done Editing, then Click on Save to save the Changes.

Step 16: On the right top corner you will get an option to pin to Azure Dashboard. If you don’t have one you can create one. 

Step 17: Go to Dashboards and Check the Preview.

That’s it you are done.

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources...
Read more

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed withou...
Read more