Book Image

Hands-On Cloud Solutions with Azure

By : Greg Leonardo
Book Image

Hands-On Cloud Solutions with Azure

By: Greg Leonardo

Overview of this book

Azure provides cloud-based solutions to support your business demands. Building and running solutions on Azure will help your business maximize the return on investment and minimize the total cost of ownership. Hands-On Cloud Solutions with Azure focuses on addressing the architectural decisions that usually arise when you design or migrate a solution to Microsoft Azure. You will start by designing the building blocks of infrastructure solution on Azure, such as Azure compute, storage, and networking, followed by exploring the database options it offers. You will get to grips with designing scalable web and mobile solutions and understand where to host your Active Directory and Identity Solution. Moving on, you’ll learn how to extend DevOps to Azure. You will also beneft from some exciting services that enable extremely smooth operations and streamlined DevOps between on-premises and cloud. The book will help you to design a secure environment for your solution, on both the Cloud and hybrid. Toward the end, you’ll see how to manage and monitor cloud and hybrid solutions. By the end of this book, you will be armed with all the tools and knowledge you need to properly plan and design your solutions on Azure, whether it’s for a brand new project or migration project.
Table of Contents (16 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Dashboards


Azure dashboards are resources that are represented as JSON behind the scenes, which means the top level properties are ID, name, location, and tags. However, these don't really have much to do with dashboards. 

Note

The type property for all dashboards is Microsoft.Portal/dashboards and the location property indicates the primary geographic location that stores the dashboard JSON because dashboards do not have a runtime component.

The properties object contains two elements, called lenses and metadata. Lenses contain the parts of the dashboard and metadata is for future features. Input values are also allowed for the dashboard component, such as the App Service or VM that are supplying the data. Let's take a look at a dashboard in Azure in the following screenshot:

Azure Dashboard

When I started using Azure dashboards, I had to create a new one each time I changed what I wanted to display between environments, for Dev, QA, and Prod. This was very difficult to manage and support; however...