Monitoring Azure Virtual Machines with CNL Metrics and Logs

It’s crucial to monitor Azure resources for availability, performance, and operation when you have key applications and business processes that rely on them. This article outlines the monitoring data created by Azure virtual machines (VMs), as well as how to analyze and alert on this data using the features of CNIL Metrics and Logs.

We recently announced the Metrics and Logs 7.7 release that adds Microsoft Azure performance monitoring for virtual instances, databases, and other resources.

You may now filter by tenancy, management group, or subscription to see all of your virtual machines (instances) and SQL instances operating on Microsoft Azure.

Metrics & Logs retains the data across months and years, allowing for both short-term and long-term performance monitoring (based on your configuration). As all data is stored on the appliance, you can expect very fast and over the top performance query possibilities and benefit from the over the top dashboards. 

What is Microsoft Azure?

Microsoft Azure is a versatile cloud computing platform that supports over 200 products and services that are available through the internet and is widely used for development and testing. Its adaptability, as well as the ability to deploy applications in minutes, make it an invaluable tool for most businesses. Azure manages and maintains the hardware, infrastructure, and resources that may be used for free or on a pay-per-use, on-demand basis, similar to other public cloud platforms.

In the workplace, Microsoft Azure is a popular choice, with Microsoft claiming Azure is used by 95% of Fortune 500 enterprises.

Customers that subscribe to Azure get access to all of the services available through the Azure portal. These services allow subscribers to construct cloud-based resources like virtual machines and databases.

Monitoring Microsoft Azure Virtual Machines

Understanding and maintaining the health and performance of the apps operating on Microsoft Azure might be difficult because it is a complex cloud service. The usage of Azure monitoring tools is required for this. By collecting, evaluating, and acting on telemetry from your cloud and on-premises settings, the CNIL Metrics and Logs tool helps you keep your services up and operating. It gives you a complete insight into your apps and assists you in identifying and resolving issues that may be hurting their performance.

You may access and examine basic information about the virtual machines deployed in your Azure VM environment using CNIL Metrics and Logs, from availability to performance history. Get a bird’s eye view of all your virtual machines in the Azure environment and keep tabs on their health and operating conditions.

Monitoring Azure VM Metrics with CNL Metrics and Logs

Virtual machines must be monitored to maintain track of their performance and health. CNL Metrics and Logs provides an interactive interface for monitoring Azure Virtual Machine performance information.

The following are the five main statistics:

  • CPU Usage
  • Disk Read Operations/Sec
  • Disk Write Operations /Sec
  • Network in
  • Network out

CPU Usage

When there is a performance issue in an application, the most typical metric to check is CPU %. It provides a percentage representation of the processor’s use. In the screenshot below, you can see that half-hour is selected, and the maximum usage is at 1.91.

Disk Read Operations/Sec

Disk input/output procedures are another aspect that affects performance. The quantity of data read from a disc per second is measured in disc read operations/second. Performance concerns can be overcome by employing a faster disc if read operations are performed more often on the drive.

Disk Write Operations /Sec

Disk write operations/sec, on the other hand, quantifies the quantity of data written per second. If the program requires a high volume of data to be written to the disc, a larger disc might be used.

Network In

The ‘network in’ area may be used to keep track of network traffic. The received network-in statistics might be expressed in bytes or TCP segments.

Network Out

TCP segments transmitted per second are discussed in network-out statics.

Start a free Trial!

Wrapping Up

With the latest version of CNL Metrics and Logs 7.7, you can easily and confidently monitor the performance of your Microsoft Azure VMs. It has a dashboard with a lot of information that might be quite useful for monitoring your Azure setup.

It allows you to create Azure monitoring dashboards that allow you to collect and monitor Azure application, performance, and infrastructure information in one location. To get a hands-on experience with CNL Metrics and Logs, sign up for a free trial, or schedule a demo for a guided tour.

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.