Gain insights into DevOps in Azure, delve into configuration management, CI/CD, and Infrastructure as Code. Explore tools like GitHub and Kubernetes through hands-on projects to become a DevOps professional.

admintodevops.tar.gz

Username

Password

AZURE_SUBSCRIPTION_ID

AZURE_CLIENT_ID

AZURE_SECRET

AZURE_TENANT

Git_Email

Git_Name

Azure

Ansible

Chrome

vscode 

Azure-VM

Terraform

az-boards

azure-instances

azure-pipelines

Docker

This course is for anyone in IT or software engineering who wants to learn more about DevOps and, specifically, how to follow DevOps practices in Azure. Whether you’re a system administrator, engineer, developer, or IT manager, this course will help you understand what it takes to deliver more value to customers with DevOps.

You will dive into concepts like configuration management, continuous integration/continuous delivery, and Infrastructure as Code. You will learn the key tools used by DevOps professionals such as: the command line, Visual Studio Code, GitHub, Kubernetes, and more.

You will complete various projects throughout the course where each chapter’s project is designed in a step-by-step manner to walk you through using the tool just as you would in your daily life.

By the time you finish, you will have the foundations in place to become a DevOps professional.

The Complete Guide to DevOps in Azure

# Monitoring 
Monitoring an application or a system has traditionally been done with popular tools like [Nagios](https://www.nagios.org/) or [PRTG](https://www.paessler.com/prtg). The monitoring tool is a separate (and distinct) application than the application it’s monitoring. Your organization must care for, manage, feed, and typically have a dedicated person or team working with it. A separate tool to monitor an application or system doubles the effort. Your organization ends up spending a lot of time monitoring the monitoring tool! It’s an entirely separate component you now have to be responsible for.

On the flip side, if you're in Azure, monitoring is built-in. You don't have to worry about maintaining the server that the monitoring tool is running on or dedicating a team for management. Instead, you have all of the tools needed for application monitoring, server monitoring, code monitoring, and even container monitoring. In this chapter, we'll take a look at just that.



Most monitoring solutions target one specific component or area of an application or infrastructure like monitoring hardware resources or application components, but Azure monitoring is different. Monitoring in Azure consists of different “layers” of monitoring built right in.

The term “Azure monitoring” encompasses a wide range of monitoring functionality from VMs, VM guest OSes, cloud billing, containers, and applications. Primarily, there are two ways to “monitor” in Azure either through the [Azure Monitor](https://azure.microsoft.com/en-us/services/monitor/#:~:text=Azure%20Monitor%20collects%20monitoring%20telemetry,optimized%20for%20cost%20and%20performance.) service or via the simple monitoring interface for the various resources.

# Built-in Azure resource monitoring

Many resources in Azure have built-in ways to do some simple monitoring. You can find this ability on many resource **Overview** blades, the **Activity Log,** or perhaps the **Diagnose and solve problems** blade. For example, take a look at the screenshot below of monitoring an Azure Virtual Machine. It shows the average CPU, network bandwidth, disk bytes, and disk operations. Built-in resource monitoring allows you to query all the way back 30 days. This service is built into the cost of the VM.


Learn how to monitor different types of resources in Azure. 