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

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

Agile Retrospective

Image
  Guide to agile retrospectives for continuous improvement An agile retrospectives is an opportunity for agile development teams to reflect on past work together and identify ways to improve. Agile teams hold retrospective meetings after a time-boxed period of work is complete (typically a sprint lasting two to four weeks). During the agile retrospective, the team discusses what went well, what did not go as planned, and how to make the next work period better. Even if you are not on a development team, you can probably relate to the concept of retrospection. Have you ever worked hard on something only to realize later that you should have done it differently? It is not always a good feeling, but the solutions you uncover in hindsight can be valuable input for your next try. The same goes for your successes — acknowledging what went well and is worth repeating can be just as impactful. What is an agile retrospective? In short, an agile retrospective is a meeting...
Read more

Agile product management

Image
  What is agile product management? How do we define agile product management? It is a product development philosophy that emphasizes a flexible and human — rather than a rigid process- or tool-oriented — approach to defining product strategy and carrying out work. Teammates focus heavily on customer feedback to make improvements and adjust roadmaps throughout the product management process. This creates more responsive teams, leads to quicker iterations, and creates a more lovable experience overall. Benefits of agile product management Agile redefines how product managers think about planning and building products. Traditionally, new customer experiences were planned, designed, implemented, and tested in a step-by-step way. This meant that new functionality was delivered sequentially. Once requirements were defined and handed off to the development team, it was difficult to make any changes. The failure rate of large-scale and lengthy software development proj...
Read more