Monitoring Azure SQL Managed Instance with CNL Logs and Metrics

When you have critical applications and business processes that rely on Azure resources, it’s critical to keep an eye on their availability, performance, and operation. This article describes how to evaluate and alert on monitoring data generated by Azure SQL Managed Instance using the CNIL Metrics and Logs., and with the release of Metrics and Logs 7.7, you can easily monitor your virtual machines, databases, and other critical resources.

To see all of your virtual machines (instances) and SQL instances running on Microsoft Azure, you may now filter by tenancy, management group, or subscription. CNL Metrics and Logs keeps track of data across months and years, allowing for both short- and long-term performance analysis (based on your configuration).

What is Microsoft Azure?

Microsoft Azure is a powerful cloud computing platform that supports over 200 internet-based products and services and is frequently used for development and testing for businesses of any size. Its versatility, as well as the ability to deploy apps in minutes, make it an indispensable tool for most enterprises. Azure, like other public cloud platforms, administers and maintains the hardware, infrastructure, and resources that may be accessed for free or on a pay-per-use, on-demand basis.

Microsoft Azure is a popular choice in the modern era, with Microsoft claiming Microsoft Azure is utilized by 95% of Fortune 500 companies.

Azure subscribers get access to all of the services accessible through the Azure portal, and subscribers can develop cloud-based resources such as virtual PCs and databases using these services.

Monitoring Azure SQL Managed Instance

Azure SQL Managed Instance is a smart, scalable cloud database solution that combines SQL Server compatibility with all the benefits of a fully managed and evergreen platform-as-a-service.

SQL Managed Instance is nearly 100 percent compatible with the newest SQL Server (Enterprise Edition) database engine, offering a native virtual network (VNet) implementation that tackles common security issues, as well as a business model for SQL Server customers.

Existing SQL Server users may use SQL Managed Instance to migrate their on-premises applications to the cloud with minimum application and database modifications. At the same time, SQL Managed Instance keeps all PaaS capabilities (automated backups, high availability, and automatic patching and version upgrades) decreasing maintenance time and expense.

Because Microsoft Azure is a sophisticated cloud service, it may be challenging to understand and manage the health and performance of the apps that run on it. The CNIL Metrics and Logs tool assists you in keeping your services up and running by collecting, assessing, and acting on telemetry from the cloud and on-premises settings. It provides you with a comprehensive view of your apps and supports you in finding and fixing issues that may be causing them to perform poorly.

CNL Logs and Metrics for Azure SQL Managed Instance Monitoring

CNIL Metrics and Logs is a monitoring tool for SQL Server instances in Azure SQL Virtual Machines, Azure SQL managed instances, Azure SQL databases, and SQL Server instances in Azure SQL managed instances. In CNIL Metrics and Logs you may instantly monitor a range of resource metrics. You may use these metrics to check if a database is using all of its processing, memory, or IO resources. The presence of a high processor percentage, as well as a high IO %, suggests that your task may require additional CPU or IO resources. It might also point to questions that need to be improved.

To monitor the Azure SQL Managed Instance, CNIL Metrics and Logs gathers CPU, storage space, virtual cores, IO read/write bytes, and IO requests.

Available Metrics to Monitor Azure SQL Managed Instance

The following are some key metrics to keep an eye on to improve the performance of your Azure SQL Managed Instance:

  • avg_cpu_percent: is a percentage that indicates the average CPU use.
  • io_bytes_read: is IO bytes read, which is a unit of measurement in bytes.
  • io_bytes_written: is written in IO bytes and also measured in bytes.
  • io_requests: is the number of IO requests counted in req/s.
  • reserved_storage_mb: Storage space has been set aside.
  • storage_space_used_mb: is a type of storage space that is used to store data and is measured in megabytes (MBs).
  • virtual_core_count: The processor’s virtual cores are counted and measured in Mhz.

Wrapping Up

It’s critical to evaluate resource usage and any performance concerns for production workloads running on your Azure SQL Database managed instance so you can respond quickly and keep your business running smoothly. Microsoft cloud-native, on-premises products, bespoke solutions, and third-party solutions are all choices for monitoring and alerting managed instances that might be evaluated.

CNIL Metrics and Logs assist you in keeping your services operational. It also provides you with a comprehensive view of your apps, assisting you in finding and fixing any issues that may be affecting their performance.

Start your trial

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.